[this is a repost of my http://shardquery.com blog post, because it did
not syndicate to planet.mysql.com]
As work on WarpSQL (Shard-Query 3) progresses, it has outgrown
MySQL proxy. MySQL proxy is a very useful tool, but it
requires LUA scripting, and it is an external daemon that needs
to be maintained. The MySQL proxy module for Shard-Query
works well, but to make WarpSQL into a real distributed
transaction coordinator, moving the proxy logic inside of the
server makes more sense.
The main benefit of MySQL proxy is that it allows a script to
"inject" queries between the client and server, intercepting the
results and possibly sending back new results to the client.
I would like similar functionality, but inside of the
For example, I would like to implement new SHOW commands, and
these commands do not need to be …[Read more]