Eric Day: Debug Console in drizzled, Part 2
About a month ago I blogged about the debug console I was adding to drizzled. I finished this work up and it’s now in the trunk and latest release. This is implemented using the Client and Listen plugin points (which are heavily modified versions of MySQL’s Protocol class), and can be enabled using the ‘–console-enable’. For example:
hades> drizzled --datadir=/Users/eday/drizzle.data --console-enable InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins. 090928 15:22:07 InnoDB: highest supported file format is Barracuda. 090928 15:22:07 InnoDB Plugin 1.0.3 started; log sequence number 46409 Listening on :::4427 Listening on 0.0.0.0:4427 ./drizzled/drizzled: Forcing close of thread 0 user: '(null)' ./drizzled/drizzled: ready for connections. Version: '2009.09.1144' Source distribution (trunk) drizzled> show tables in information_schema; Tables_in_information_schema INNODB_TRX INNODB_LOCKS ... STATISTICS TABLE_CONSTRAINTS TABLES drizzled> ./drizzled/drizzled: Forcing close of thread 1 user: '(null)' ./drizzled/drizzled: Normal shutdown 090928 15:22:31 InnoDB: Starting shutdown... 090928 15:22:32 InnoDB: Shutdown completed; log sequence number 46419 ./drizzled/drizzled: Shutdown complete hades>
You can type ‘quit’, ‘exit’, or just send EOF (CTRL-D) to shutdown drizzled. There is another patch along the way with some fixes to make it more efficient for mas imports (ie, drizzled –console-enable data_dump.sql). It’s pretty bare bones now, but patches welcome for new features to make this look more like the normal command line tool (like changing prompt).
URL: http://oddments.org/?p=147
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
