On Aug 5, 2008, at 1:00 PM, Paul McCullagh wrote:
Also the behaviour could be made switchable, not everybody needs a
query log.
Yes, this would make sense.
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. Any
clientside additions can only be done at a much later stage, such as
pre-parsing and sending serialized trees.
I'm sure we'll find a clean way to support query logging then, too. If
nothing else we can rewrite portions of the code and/or change the
relevant protocol commands (note that the "normal" way of sending
query text is unaffected by all this, so that would remain stable).
Starting next weekend I should have time to do the initial work on this.
cheers,
-k
--
Kay Roepke
Software Engineer, MySQL Enterprise Tools
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
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
