Transaction Log startup variables cannot be placed in drizzled.cnf

[Jay Pipes]

Placing in the [drizzled] section of /etc/drizzled.cnf:

transaction_log_enable

produces:

InnoDB: The InnoDB memory heap is disabled
InnoDB: Neither mutexes nor rw_locks use GCC atomic builtins.
100330 4:26:44 InnoDB: highest supported file format is Barracuda.
100330 4:26:45 InnoDB Plugin 1.0.4 started; log sequence number 44274
./drizzled: unknown option '--transaction_log_enable
'Aborting
100330 4:26:45 InnoDB: Starting shutdown...
100330 4:26:46 InnoDB: Shutdown completed; log sequence number 44284

[Jay Pipes (jaypipes)]

This has to do with bugs in the processing and parsing of plugin variables in general.

For instance, putting the following in a config file:

[drizzled]
transaction_log_enable=1

works, but these do not:

transaction_log_enable=on
transaction_log_enable=true

[Jay Pipes (jaypipes)]

So, this is kind of solved, but variable and config file processing needs a complete overhaul.

[Jay Pipes (jaypipes)]

Setting to confirmed since my fix had Python test components, which shouldn't be used.

[Lee Bieber (kalebral-deactivatedaccount)]

Invalid - now all options in the config file have to be under categories and it should not have any underscores