On Mon, Apr 06, 2009 at 03:28:33PM -0400, Jay Pipes wrote: > >> Not sure if I agree here. I think a pre-parser plugin/module would > >> be better than sticking this in the client library. This way we > > > > A query rewriter before the parser call would be pretty damn simple... > > Yeah, but the problem is then we basically make this a required, > built-in module for everyone, since this functionality would be required > for everyone pretty much....
It is by no means required, but we would probably ship it on by default (just like other common plugins). If a user knows they will never want the MySQL style SHOW mappings, they can just disable it in the config. This is a great way to do other temporary compatibility mappings until common tools officially support Drizzle. I agree it is not ideal, but I think it's a bit cleaner than pushing this down into the client library. -Eric _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
