On Mon, Aug 18, 2008 at 10:29 PM, Jay Pipes <[EMAIL PROTECTED]> wrote: > Brian Aker wrote: >> Hi! >> >> On Aug 18, 2008, at 6:44 PM, Baron Schwartz wrote: >> >>> Yeah, do we really need SHOW anymore at all? I would argue not. >> >> I go back and forth on this. >> >> Right now I believe: >> 1) Keeping them in the client I think is a win. >> 2) Right now we need them because for replication not everything is in I_S. >> 3) SHOW CREATE TABLE is required no matter what... or we have to find >> some similar syntax (I personally find it really useful). > > Again, I return to the idea that SHOW and other commands like DESC can > be implemented as a raw string replacement on the client. Basically, > convert SHOW TABLES to SELECT TABLE_NAME.TABLE FROM INFORMATION_SCHEMA, > etc... > > As for SHOW CREATE TABLE, besides the comment given in the create > statement (which we currently are planning to store using Proto Buffers > in Field::comment()) is there anything about the SHOW CREATE TABLE > statement that *cannot* be generated from schema information stored in I_S?
It's true that it's damn useful. Maybe we need a function to convert from I_S to SHOW CREATE syntax we all know and love: select SYS_SHOW_CREATE(@db, @tbl); At least then it can be manipulated like a first-class piece of data. You can assign it to variables or store it in tables or whatever you want. I do not like client-side conversions from SHOW to SELECT. All that does is put a parser into the client. And now you have syntaxes that seem to be valid SQL, yet the daggone server doesn't recognize them. *wags finger in the air* mark my words this will come back to haunt... if it doesn't feel "clean" there's probably a reason to rethink it. And this smells really really bad. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
