[MDEV-4533] TokuDB: IGNORE clause doesn't work with ROW binlog format Created: 2013-05-15 Updated: 2014-05-06 Resolved: 2014-05-06 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.36, 10.0.10 |
| Fix Version/s: | 5.5.38, 10.0.11 |
| Type: | Bug | Priority: | Trivial |
| Reporter: | Elena Stepanova | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tokudb, upstream | ||
| Issue Links: |
|
||||||||
| Description |
|
When binary log is enabled in ROW format, statements like DELETE IGNORE ... etc. fail with ER_BINLOG_ROW_MODE_AND_STMT_ENGINE (Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging), while the same statements without IGNORE are executed all right. It works the same way on MariaDB-5.5.30-TokuDB-7.0.1, but it would be good to make sure it's an intentional limitation and not an oversight.
Test case (for MariaDB):
bzr version-info
|
| Comments |
| Comment by Rich Prohaska [ 2014-04-13 ] |
|
the workaround is to set tokudb_pk_insert_mode=2. |
| Comment by Rich Prohaska [ 2014-04-28 ] |
|
fixed in tokudb 7.1.6 |