11–20 of 26 posts
Oh, and it becomes painfully obvious why MySQL cannot use more than one index while executing the query.
https://dev.mysql.com/doc/refman/5.7/en/index-merge-optimiza...
Oh, and it becomes painfully obvious why MySQL cannot use more than one index while executing the query.
Can PostgreSQL use more than one index per table while executing a query?
Somewhat related, I recently started trying to reverse-engineer the MySQL wire protocol. My idea is that if this is better documented then it will be easier for people to make databases that interoperate with MySQL clients but aren't MySQL that much easier (personally I want a custom Shard-Query-ish thing). This is obstinately documented ( http://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_PROTOC... ), but I can't…
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-protoc... http://imysql.com/mysql-internal-manual/connection-phase.htm... http://imysql.com/mysql-internal-manual/com-query.html etc
We're working on moving the internals documentation into the server code with Doxygen: http://mysqlserverteam.com/mysql-8-0-now-documented-with-dox...
Am I the only one who likes the "C with classes" approach over C++?
Earlier quoted context omitted.
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-protoc... http://imysql.com/mysql-internal-manual/connection-phase.htm... http://imysql.com/mysql-internal-manual/com-query.html etc
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-dox...
- 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_protoc...
Earlier quoted context omitted.
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-protoc... http://imysql.com/mysql-internal-manual/connection-phase.htm... http://imysql.com/mysql-internal-manual/com-query.html etc
Crikey, thx. There's a lot of dead links, e.g. http://imysql.com/mysql-internal-manual/com-query.html doesn't describe the response? Got any idea what a query response consists of?
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/proto...
Earlier quoted context omitted.
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-dox...
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_protoc... - https://dev.mysql.com/doc/dev/mysql-server/8.0.0/page_protoc...
Somewhat related, I recently started trying to reverse-engineer the MySQL wire protocol. My idea is that if this is better documented then it will be easier for people to make databases that interoperate with MySQL clients but aren't MySQL that much easier (personally I want a custom Shard-Query-ish thing). This is obstinately documented ( http://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_PROTOC... ), but I can't…
It's a few years old now, and maybe unsupported, but it was a cleanroom re-implementation by former MySQL devs, and is likely cleaner as a result.
Am I the only one who likes the "C with classes" approach over C++?