TIME datatype is not supported (MCOL-392)

[MCOL-1418] TIME: LDI saturates out-of-range values incorrectly Created: 2018-05-15  Updated: 2018-06-18  Resolved: 2018-06-18

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.0

Type: Sub-Task Priority: Major
Reporter: Daniel Lee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2018-08, 2018-09, 2018-10, 2018-11, 2018-12, 2018-13, 2018-14, 2018-15, 2018-16, 2018-17, 2018-18

 Description   

LDI Saturated to max supported values (839:59:59) for both positive and negative out of range values. The negative out-of-range value should be saturated to -839:59:59.

 Comments   
Comment by Daniel Lee (Inactive) [ 2018-05-15 ]

The issue occurs even when not saturating. LDI the min value of -838:59:59 would also end up with 838:59:59.

Comment by Andrew Hutchings (Inactive) [ 2018-06-07 ]

MySQL binary time conversion was missing negative flag. Fixed in a branch full of fixes for MCOL-392

Comment by Andrew Hutchings (Inactive) [ 2018-06-07 ]

Pull request in engine and regression suite to cover this.

Comment by Daniel Lee (Inactive) [ 2018-06-18 ]

Build verified: 1.2.0-1 source

/root/columnstore/mariadb-columnstore-server
commit 3bfc3ad5f1e91e6f325b89fefaf62a6b38ca889a
Merge: 4334641 742af4d
Author: David.Hall <david.hall@mariadb.com>
Date: Thu May 31 09:40:12 2018 -0500

Merge pull request #119 from mariadb-corporation/1.1-merge-up-20180531

Merge develop-1.1 into develop

/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit 1caa98ff46777a389cdfd4ae369865391a884c27
Merge: 60a4d14 d9e6ba9
Author: David.Hall <david.hall@mariadb.com>
Date: Mon Jun 11 10:20:49 2018 -0500

Merge pull request #494 from mariadb-corporation/MCOL-1433

MCOL-1433 Fix several functions for TIME handling

Generated at Thu Feb 08 02:28:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.