Tables without a PK are being logged to the transaction log
Bug #652394 reported by
David Shrewsbury
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Invalid
|
Undecided
|
Unassigned | ||
| 7.0 |
Invalid
|
Medium
|
David Shrewsbury | ||
Bug Description
If a table is created without a Primary Key with transaction logging enabled, the CREATE TABLE statement is ending up in the transaction log, even though no events for it will appear in the log.
| Changed in drizzle: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| milestone: | none → 2010-10-11 |
| milestone: | 2010-10-11 → none |
| importance: | Medium → Undecided |
| Changed in drizzle: | |
| assignee: | David Shrewsbury (dshrews) → nobody |
Revision history for this message
| David Shrewsbury (dshrews) wrote | #1 |
| Changed in drizzle: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
I don't believe this is a bug. I don't think the original intent was to forbid replicating DDL statements if they do not have a primary key. We don't have such checks on DELETE TABLE, TRUNCATE TABLE, ALTER TABLE, etc. We only warn that we cannot replicate a DML statement when it is for a table without a PK because one is necessary for the type of row-based replication that we do.