FLUSH TABLE, and then UNLOCK TABLES in a different connection gives you zero warnings/etc
Bug #682006 reported by
Brian Aker
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Medium
|
Stewart Smith | ||
| 7.0 |
Fix Released
|
Medium
|
Stewart Smith | ||
Bug Description
Calling unlock tables in the connection that did not call flush tables reports nothing, ie it should be an error since as an action it did nothing.
Related branches
lp:~stewart/drizzle/bug682006-unlock-no-tables-error
- Drizzle Developers: Pending requested
-
Diff: 123 lines (+36/-4)9 files modifieddrizzled/error.cc (+1/-1)
drizzled/error_t.h (+2/-1)
drizzled/statement/unlock_tables.cc (+6/-2)
tests/r/flush.result (+1/-0)
tests/suite/flush_tables/r/update_select.result (+1/-0)
tests/suite/flush_tables/t/update_select.test (+1/-0)
tests/suite/regression/r/682006.result (+7/-0)
tests/suite/regression/t/682006.test (+16/-0)
tests/t/flush.test (+1/-0)
| Changed in drizzle: | |
| assignee: | nobody → Brian Aker (brianaker) |
To post a comment you must log in.
