Put everything in the I_S
And then either in pre-parse in the server, or else in a rewriter in
the command line tool, turn the SHOW commands into SELECTS against the
I_S
The server shouldnt know about SHOW at all.
On Jul 17, 2008, at 8:25 AM, Brian Aker wrote:
Hi!
Welcome to the incompatible command discussion!
Here is the thing, SHOW commands are done in the parser and just
bulk it up. Some of them are invaluable, all of them should go into
the new I_S.
SHOW CREATE TABLE is a "must have". Why is that? It is our de-
serializer at this point. AKA the way we tell mysqldump what the SQL
structure is.
The replication commands are not completely replicated into I_S, and
show table status is its own unique thing.
What must we keep? Where is the line in the sand? Is there a line in
the sand?
Keep in mind I do not mind incompatibilities, but they all need a
justification. When it comes to show I do not wish to break millions
of apps, but I do not want to keep old cruff because we fear
breaking with the past. I see people building new applications
around drizzle, not necessarily porting old (though there will be
plenty of that).
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
--
Mark Atwood <http://mark.atwood.name>
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
