Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.6, 10.3(EOL), 10.4(EOL), 10.5(EOL), 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
-
None
-
Unexpected results
Description
Test case from the description of MDEV-14794 works now for timestamps, but still causes troubles with transaction IDs:
create or replace table t1 (pk int primary key, i int, |
s bigint unsigned as row start, |
e bigint unsigned as row end, period for system_time(s,e)) |
engine=InnoDB with system versioning; |
replace into t1 (pk,i) values (1,10),(1,100),(1,1000); |
10.3 c39f8a80c9fe |
MariaDB [test]> replace into t1 (pk,i) values (1,10),(1,100),(1,1000); |
ERROR 1062 (23000): Duplicate entry '1-18446744073709551615' for key 'PRIMARY' |
Same for stored functions and probably for triggers.
Attachments
Issue Links
- causes
-
MDEV-37404 InnoDB: Failing assertion: node->pcur->rel_pos == BTR_PCUR_ON
-
- Confirmed
-
- is blocked by
-
MDEV-30238 LOAD DATA REPLACE into ucs2-encoded FK field fails
-
- Closed
-
- is duplicated by
-
MDEV-35343 unexpected replace behaviour when long unique index on system versioned table
-
- Closed
-
- relates to
-
MDEV-30046 wrong row targeted with "insert ... on duplicate" and "replace", leading to data corruption
-
- Closed
-