Part of what makes MySQL so accessible and easy to use is the fact that you authenticate and then type "SHOW DATABASES" to see what databases exist, then "USE <database>" and "SHOW TABLES" (or "SHOW TABLES FROM <database>").
And I use SHOW TABLE STATUS a lot, I forget whether the information schema shows when a table is corrupt as SHOW TABLE STATUS does. I think the commands should be valid, though I'm not opposed to "SHOW DATABASES" being parsed as "SELECT SCHEMA_NAME FROM INFORMATION_SCHEMA.SCHEMATA". Alternatively, make UDF's so simple or some other kind of easy plugin simple, so that people can write their own (or develop a library and share).....things like SHOW INNODB TABLES and SHOW MYISAM TABLES or SHOW TABLE ENGINES to get information about tables of a certain type....SHOW QUERY_CACHE STATS, SHOW TEMP_TABLE STATS, whatever. How would this affect SHOW VARIABLES and SHOW STATUS? Those are pretty useful, I think we should definitely keep 'em. -Sheeri On 7/17/08, Brian Aker <[EMAIL PROTECTED]> 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<https://launchpad.net/%7Edrizzle-discuss> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> > More help : https://help.launchpad.net/ListHelp > -- - Sheeri K. Cabral Note: Currently I work for The Pythian Group (http://www.pythian.com/ ), a remote DBA firm, and consulting would constitute a conflict of interest. However, I do recommend our work, and if you're looking for DBA work (I do MySQL work, but they have great Oracle and SQL Server DBAs too) right now, whether you need a few hours a week, or someone fulltime while you continue a job search. I have a webpage with tips on how to find a DBA: http://sheeri.net/how-to-find-a-dba/ I can recommend http://www.toomanyconnections.com as a good site to find MySQL (and Oracle) DBAs. If you're looking for web design, I recommend the small business my husband works for, http://www.digital-loom.com I regret that I have no other information for any other type of position, including developer, programmer and systems administrator.
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
