Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.4(EOL)
-
None
Description
Reproduce
create table t0 (c0 int, c1 timestamp(6), c2 timestamp(6)) with system versioning; |
insert into t0 values (0, '2000-01-01 00:00:00', c1); |
insert into t0 values (1, '2001-01-01 00:00:00', row_start); |
insert into t0 values (2, '2002-01-01 00:00:00', row_end); |
select * from t0; |
drop table t0; |
Result
select * from t0; |
c0 c1 c2
|
0 2000-01-01 00:00:00.000000 2000-01-01 00:00:00.000000
|
1 2001-01-01 00:00:00.000000 0000-00-00 00:00:00.000000
|
2 2002-01-01 00:00:00.000000 0000-00-00 00:00:00.000000
|
Expected
Field c2 is filled with correct values for rows 1 and 2.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description |
h3. Reproduce
{code:sql} create table t0 (c0 int, c1 timestamp(6), c2 timestamp(6)) with system versioning; insert into t0 values (0, '2000-01-01 00:00:00', c1); insert into t0 values (1, '2001-01-01 00:00:00', row_start); insert into t0 values (2, '2002-01-01 00:00:00', row_end); select * from t0; drop table t0; {code} h3. Result {code:sql} select * from t0; c0 c1 c2 0 2000-01-01 00:00:00.000000 2000-01-01 00:00:00.000000 1 2001-01-01 00:00:00.000000 0000-00-00 00:00:00.000000 2 2002-01-01 00:00:00.000000 0000-00-00 00:00:00.000000 {code} h3. Expected Field c2 is filled with correct values for rows 1 and 2. |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Fix Version/s | 10.6 [ 24028 ] | |
Fix Version/s | 10.10 [ 27530 ] | |
Fix Version/s | 10.11 [ 27614 ] | |
Fix Version/s | 11.0 [ 28320 ] | |
Fix Version/s | 11.1 [ 28549 ] |
Fix Version/s | 10.10 [ 27530 ] |
Fix Version/s | 11.0 [ 28320 ] |
Fix Version/s | 10.4 [ 22408 ] |
Fix Version/s | 11.1 [ 28549 ] |
I'm not sure it's a bug. Better to check the standard to see how it defines when row_start/row_end get their values.