Kay,
At this point it doesn't make much difference, I think. The first step is to separate out the parser and create a decent internal API. [..]
Right. Once there is an API, we can of course have everything at the same time in different modules.
I'm sure we'll find a clean way to support query logging then, too. [..]
What about just simply logging the query that is sent by the client, but optionally overriding how it is executed by sending byte code or a tree?
I can think of many cases where even a client that uses SQL might want to log something different from the exact query it uses, e.g. an ORM might want to attach information about which *code* resulted in the query. Would make it much easier to debug these things, especially for devs who don't know SQL too well. Try to figure out what hibernate is doing if you're working on one-two years of Java experience and nothing else...
Daniel -- Daniel Fischer, MySQL Team Lead Build +46 18174400 ext. 4537 Sun Microsystems GmbH Sonnenallee 1, DE-85551 Kirchheim-Heimstetten Geschaeftsfuehrer: Thomas Schroeder, Wolfang Engels, Dr. Roland Boemer Vorsitz d. Aufs.rat.: Martin Haering HRB MUC 161028 49.011, 8.376 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
