Tables with no primary key, should avoid certification
Bug #605594 reported by
Seppo Jaakola
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL patches by Codership |
Fix Released
|
Medium
|
Seppo Jaakola | ||
| 0.7 |
Fix Released
|
Medium
|
Seppo Jaakola | ||
| 0.8 |
Fix Released
|
Medium
|
Seppo Jaakola | ||
Bug Description
Currently, if there is no primary key/unique index in a table, wsrep copies the hidden key generated by innodb (6 bytes) in write set key column. This is wrong practice as innodb keys are private for each node and cannot be compared in certification.
Related branches
lp:~codership/codership-mysql/dev
(Merged)
| Changed in codership-mysql: | |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
| milestone: | none → 0.7.5 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #1 |
| Changed in codership-mysql: | |
| status: | In Progress → Fix Committed |
| Changed in codership-mysql: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
A fix has been committed to skip tables without PK in certification. However, a later bug: lp:616757 works on this further by making it possible (and optional) to generate artificial PK for such tables.