[MDEV-14764] Confusing error message: Table `t1` must have at least one temporal column Created: 2017-12-25  Updated: 2018-01-09  Resolved: 2017-12-27

Status: Closed
Project: MariaDB Server
Component/s: Versioned Tables
Affects Version/s: N/A
Fix Version/s: 10.3.4

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None
Environment:

bb-10.3-temporal ea49441c41



 Description   

This is yet another case where I think the use of "temporal" is quite confusing:

MariaDB [test]> CREATE OR REPLACE TABLE t1 (s TIMESTAMP(6) GENERATED ALWAYS AS ROW START, e TIMESTAMP(6) GENERATED ALWAYS AS ROW END, PERIOD FOR SYSTEM_TIME (s,e)) WITH SYSTEM VERSIONING;
ERROR 4128 (HY000): Table `t1` must have at least one temporal column

Unless the wording is regulated by the standard, I'd suggest to change it. I think for an average user, if anything is "temporal" here, it's columns `s` and `e`, as they directly related to time, both by type and purpose. The next thought is that on some reason we require the table to have a column of a "temporal data type" (expression that is already used here and there); and only after all that one can start guessing that something else is meant.



 Comments   
Comment by Sergei Golubchik [ 2017-12-27 ]

pushed into bb-10.3-temporal-serg

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