Transaction Log startup variables cannot be placed in drizzled.cnf

Bug #551075 reported by Jay Pipes on 2010-03-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Medium
Unassigned
Cherry
Medium
David Shrewsbury

Bug Description

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) wrote :

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) wrote :

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

Jay Pipes (jaypipes) on 2010-05-10
Changed in drizzle:
milestone: 2010-05-10 → 2010-06-07
Lee Bieber (kalebral) on 2010-06-08
Changed in drizzle:
milestone: 2010-06-07 → none
Jay Pipes (jaypipes) wrote :

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

Changed in drizzle:
status: Fix Committed → Confirmed
assignee: Jay Pipes (jaypipes) → nobody
Lee Bieber (kalebral) wrote :

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

Changed in drizzle:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers