--engine in dbqp.py is broken
Bug #709646 reported by
Vijay Samuel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Fix Released
|
Low
|
Patrick Crews | ||
7.0 |
Fix Released
|
Low
|
Patrick Crews |
Bug Description
python dbqp.py --engine=memory still runs innodb. providing invalid storage engine names also runs innodb. invalid storage engine names must throw errors and log them.
Related branches
lp:~patrick-crews/drizzle/dbqp_engine_and_repeat
- Drizzle Developers: Pending requested
-
Diff: 188 lines (+49/-12)7 files modifieddocs/testing/dbqp.rst (+5/-0)
tests/dbqp.py (+4/-2)
tests/lib/server_mgmt/drizzled.py (+9/-2)
tests/lib/server_mgmt/server_management.py (+10/-2)
tests/lib/test_mgmt/execution_management.py (+1/-0)
tests/lib/test_mgmt/test_execution.py (+7/-5)
tests/lib/test_run_options.py (+13/-1)
Changed in drizzle: | |
status: | Confirmed → Fix Committed |
milestone: | none → 2011-02-14 |
Changed in drizzle: | |
milestone: | 2011-02-14 → 2011-02-28 |
Changed in drizzle: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Will rename to --default- storage- engine and will add code to handle this appropriately.
Option was largely a placeholder while I got the rest of the system working - thanks for the reminder! : )