[MDEV-15408] Confusing error message upon ER_VERS_FIELD_WRONG_TYPE while omitting UNSIGNED in BIGINT Created: 2018-02-24  Updated: 2019-08-05  Resolved: 2019-08-05

Status: Closed
Project: MariaDB Server
Component/s: Versioned Tables
Affects Version/s: 10.3
Fix Version/s: 10.3.16, 10.4.5

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Eugene Kosov (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-16144 Default TIMESTAMP clause for SELECT f... Closed
is blocked by MDEV-16130 wrong error message adding AS ROW STA... Closed

 Description   

bb-10.3-release 9b59f78d16fb000ad

MariaDB [test]> create or replace table t3( id int, row_start bigint as row start, row_end bigint as row end, period for system_time (row_start, row_end) ) with system versioning;
ERROR 4108 (HY000): `row_start` must be of type TIMESTAMP(6) for system-versioned table `t3`

It took me a while to figure why it wasn't accepting my explicitly defined BIGINT and insisting on TIMESTAMP instead; it turns out that I've actually missed UNSIGNED. While I understand that the server can't guess what the user implied, maybe it could be made better somehow.



 Comments   
Comment by Eugene Kosov (Inactive) [ 2018-03-28 ]

https://github.com/MariaDB/server/pull/677

Generated at Thu Feb 08 08:21:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.