On Sun, Apr 5, 2009 at 12:37 PM, Brian Aker <[email protected]> wrote:
> Hi! > So I am of the school of thought that most SHOW commands should go to the > command line client and be purged from parser. Ronald wrote the following > article: > > http://ronaldbradford.com/blog/a-beginners-look-at-drizzle-getting-around-with-show-2009-03-31/ > > Here is a list of current show commands: > > SHOW COLUMNS FROM information_schema.tables; > > SHOW CREATE DATABASE information_schema; > > SHOW DATABASES; > > SHOW ENGINE INNODB STATUS; > > SHOW ERRORS; > > SHOW INDEX FROM information_schema.tables; > > SHOW OPEN TABLES; > > SHOW PROCESSLIST; > > SHOW STATUS; > > SHOW TABLE STATUS; > > SHOW TABLES; > > SHOW VARIABLES; > > SHOW WARNINGS; > > SHOW CREATE SCHEMA; > > SHOW SCHEMAS; > > Anyone have thoughts on what should stay or go? The keyword "FULL" exists for > several of these. For COLUMNS I suspect it could just be on by default. SHOW > INDEX looks odd. > > Many, many folks have integrated SHOW into their non-commandline applications. In fact, some of the basic PHP/MySQL tutorials include connecting with mysql/mysqli and running SHOW DATABASES and then SHOW TABLES. I'm pretty sure that's how utilities like PHPMyAdmin work. Not that I think there should be a PHPDrizzleAdmin (as I think PHPMyAdmin does very little other than giving a graphical interface), but it's something to consider. Many of the SHOW commands also allow a LIKE modifier. It would probably be better to keep it in the parser, but rewrite it to the correct information_schema result. As for SHOW INDEX, it is equivalent to/an alias for SHOW INDEXES, which is less awkward -- "SHOW INDEXES FROM tbl". The only problem with my idea is that it doesn't account for some things: SHOW CREATE ... (not just tables and schemas, but views, stored functions/procedures, etc) SHOW OPEN TABLES SHOW ENGINE INNODB STATUS -- this should be made into relational data of some sort, honestly, and stored in an information_schema table. SHOW WARNINGS and SHOW ERRORS -- these are ridiculous, we should always show them by default, perhaps with a "don't show" flag settable, but....the command itself is silly. -Sheeri > Other thoughts? TABLE TABLE STATUS? OPEN TABLES? > > Cheers, > > -Brian > > > > _______________________________________________ > 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 http://tinyurl.com/mysqlbook will take you to the Amazon.com page for my upcoming book, "MySQL Administrator's Bible".
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
