On Sun, Apr 5, 2009 at 10:12 AM, Sheeri K. Cabral <[email protected]> wrote: > 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.
Also, the show commands take waaaay less typing. > 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. IIRC: Recent version of phpMyAdmin (such as the 3 series which requires MySQL 5.0 or greater) makes significant use of the IS, though I have little doubt that show commands are still in code. -- Rob Wultsch [email protected] _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
