Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL)
-
None
Description
MDEV-29833 forbade (in some cases) using DEFAULT with ROW START/END columns.
It leads to the usual OM => NS replication problem which always happens when something was allowed on an older version and started causing an error on a new version. It should have been expected (I guess that's why it was only fixed in 10.11), but since my comment in MDEV-29833 doesn't say anything about it, technically it was missed in testing, so I'm filing it now. Feel free to close as "won't fix".
On a pre-10.11 master:
create table t (a int, row_start timestamp(6) as row start, row_end timestamp(6) as row end, period for system_time(row_start,row_end)) with system versioning; |
insert into t (a) values (1); |
update t set row_start = default; |
On a 10.11+ slave:
Last_SQL_Error: Error 'Field 'row_start' doesn't have a default value' on query. Default database: 'test'. Query: 'update t set row_start = default'
|
Attachments
Issue Links
- is caused by
-
MDEV-29833 CREATE ... SELECT system_versioned_table causes invalid defaults
- Closed