drizzleslap with --commit runs second iteration data load in a transaction
Bug #668143 reported by
Stewart Smith
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
High
|
Stewart Smith | ||
| 7.0 |
Fix Released
|
High
|
Stewart Smith | ||
Bug Description
At the end of the first iteration in drizzleslap, if commit_count is set, it will run SET AUTOCOMMIT=0. This means that the next load of data for the next iteration gets run in 1 transaction.
On top of this, it is a transaction that is NOT committed.
i.e. the second iteration will be running against no data.
Related branches
lp:~stewart/drizzle/slap-remove-autocommit-in-load-bug668143
- Brian Aker: Needs Fixing
- Lee Bieber (community): Needs Fixing
-
Diff: 59 lines (+0/-8)3 files modifiedclient/drizzleslap.cc (+0/-4)
plugin/haildb/tests/r/drizzleslap.result (+0/-2)
tests/r/drizzleslap.result (+0/-2)
To post a comment you must log in.
