3 ms·

Take a closer look at the MySQL documentation. You dont have to reverse engineer anything - it's all there and documented (source: wrote a client impl based on

Take a closer look at the MySQL documentation. You dont have to reverse engineer anything - it's all there and documented (source: wrote a client impl based on the docs) http://imysql.com/mysql-internal-manual/client-server-protocol.html http://imysql.com/mysql-internal-manual/client-server-protoc... http://imysql.com/mysql-internal-manual/connection-phase.html http://imysql.com/mysql-internal-manual/connection-phase.htm... http://imysql.com/mysql-internal-manual/com-query.html http://imysql.com/mysql-internal-manual/com-query.html etc

willvarfar 9y ago
Crikey, thx. There's a lot of dead links, e.g. http://imysql.com/mysql-internal-manual/com-query.html http://imysql.com/mysql-internal-manual/com-query.html doesn't describe the response? Got any idea what a query response consists of?
- ccommsxx 9y ago
  Turns out that all of this stuff has apparently been deleted from the official docs some time ago, so that's probably why you didn't find it :) (see sibling comment). When I did a quick google to pull up the docs that I knew I had read when I implemented the mysql client I found & linked you to a non-official, old copy of the mysql docs from back then. You can still find the docs for COM_QUERY result on the net though: https://github.com/cwarden/mysql-proxy/blob/master/doc/protocol.rst#com_query-response https://github.com/cwarden/mysql-proxy/blob/master/doc/proto...
morgo 9y ago
This is not the MySQL manual (dev.mysql.com) but a third party copy that is at least a few years old. We're working on moving the internals documentation into the server code with Doxygen: http://mysqlserverteam.com/mysql-8-0-now-documented-with-doxygen/ http://mysqlserverteam.com/mysql-8-0-now-documented-with-dox...
- ccommsxx 9y ago
  I can see what parents issue was now :) I had a look at the doxygen and all the goold old protocol documentation seems to be deleted/missing from the "official" documentation website. How come -- I found it really useful? - https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protocol_connection_phase.html https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protoc... - https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protocol_command_phase.html https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protoc...
  - ccommsxx 9y ago
    Actually I remembered now that the last time I worked with the MySQL protocol (~2014) I had a similar problem: Some of our servers were still running an old version of MySQL so the client had to be backwards compatible. However, this old version of MySQL also used the "old mysql password" authentication which was found to be unsafe/broken at some point. So the MySQL guys deleted the documentation on how the old scheme worked and replaced it with a notice saying that it is insecure. Tough luck if you still had to support/implement it. The same thing has apparently happened here. Not only is the documentation gone, it's actually gone without a trace on the official website.
  - morgo 9y ago
    The content is being re-incorporated in the Doxygen docs, which is generated from the source. (The internals manual was out of date in many cases. I do not recommend relying on the links mentioned here.)

willvarfar 9y ago

Crikey, thx. There's a lot of dead links, e.g. http://imysql.com/mysql-internal-manual/com-query.html http://imysql.com/mysql-internal-manual/com-query.html doesn't describe the response? Got any idea what a query response consists of?

ccommsxx 9y ago
Turns out that all of this stuff has apparently been deleted from the official docs some time ago, so that's probably why you didn't find it :) (see sibling comment). When I did a quick google to pull up the docs that I knew I had read when I implemented the mysql client I found & linked you to a non-official, old copy of the mysql docs from back then. You can still find the docs for COM_QUERY result on the net though: https://github.com/cwarden/mysql-proxy/blob/master/doc/protocol.rst#com_query-response https://github.com/cwarden/mysql-proxy/blob/master/doc/proto...

morgo 9y ago

This is not the MySQL manual (dev.mysql.com) but a third party copy that is at least a few years old. We're working on moving the internals documentation into the server code with Doxygen: http://mysqlserverteam.com/mysql-8-0-now-documented-with-doxygen/ http://mysqlserverteam.com/mysql-8-0-now-documented-with-dox...

ccommsxx 9y ago
I can see what parents issue was now :) I had a look at the doxygen and all the goold old protocol documentation seems to be deleted/missing from the "official" documentation website. How come -- I found it really useful? - https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protocol_connection_phase.html https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protoc... - https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protocol_command_phase.html https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protoc...
- ccommsxx 9y ago
  Actually I remembered now that the last time I worked with the MySQL protocol (~2014) I had a similar problem: Some of our servers were still running an old version of MySQL so the client had to be backwards compatible. However, this old version of MySQL also used the "old mysql password" authentication which was found to be unsafe/broken at some point. So the MySQL guys deleted the documentation on how the old scheme worked and replaced it with a notice saying that it is insecure. Tough luck if you still had to support/implement it. The same thing has apparently happened here. Not only is the documentation gone, it's actually gone without a trace on the official website.
- morgo 9y ago
  The content is being re-incorporated in the Doxygen docs, which is generated from the source. (The internals manual was out of date in many cases. I do not recommend relying on the links mentioned here.)