3 ms·
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
by 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 agoI 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 agoActually 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 agoThe 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.)