Transaction Log startup variables cannot be placed in drizzled.cnf
Bug #551075 reported by
Jay Pipes
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Invalid
|
Medium
|
Unassigned | ||
Cherry |
Invalid
|
Medium
|
David Shrewsbury |
Bug Description
Placing in the [drizzled] section of /etc/drizzled.cnf:
transaction_
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_
'Aborting
100330 4:26:45 InnoDB: Starting shutdown...
100330 4:26:46 InnoDB: Shutdown completed; log sequence number 44284
Related branches
Changed in drizzle: | |
milestone: | 2010-05-10 → 2010-06-07 |
Changed in drizzle: | |
milestone: | 2010-06-07 → none |
To post a comment you must log in.
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] log_enable= 1
transaction_
works, but these do not:
transaction_ log_enable= on log_enable= true
transaction_