6
:program:`console` is a protocol plugin that instead of providing access to Drizzle through a network port or UNIX socket provides a direct interactive text console via stdin and stdout. It allows you to use Drizzle in a similar way that the sqlite command line client allows you to use sqlite.
13
To load this plugin, start :program:`drizzled` with::
19
:ref:`drizzled_plugin_options` for more information about adding and removing plugins.
21
.. _console_configuration:
26
.. option:: --console.enable
32
.. option:: --consoe.debug
36
Turns on extra debugging output
38
.. option:: --console.username ARG
40
:Default: ``current logged in user``
42
The username to authenticate to Drizle as. This option works the same way as connecting as a username over other protocols.
44
.. option:: --console.password ARG
46
The password to use to authenticate with.
48
.. option:: --console.catalog ARG
52
Which catalog to connect to. In current released versions of Drizzle, only the LOCAL catalog is supported, althoug in the future other catalogs will be usable.
54
.. option:: --console.schema ARG
56
Which schema to connect to.
58
.. _console_variables:
63
This plugin does not register any variables.
70
To use the Drizzle console, start Drizzle like:
74
$ sbin/drizzled --plugin-add=console --console.enable
76
You can now interact with Drizzle in pretty much the same way you can as through the command line client.
78
You probably never want to enable the console plugin in the configuration file.
80
.. _console_limitations:
85
There is currently no way to change your authentication credentials once you've launched Drizzle with the console plugin.
93
:Documentation: Stewart Smith
100
This documentation applies to **console 0.2**.
102
To see which version of the plugin a Drizzle server is running, execute:
104
.. code-block:: mysql
106
SELECT MODULE_VERSION FROM DATA_DICTIONARY.MODULES WHERE MODULE_NAME='console'
117
* Support connecting to a CATALOG
118
* Rename db parameter to schema