[MDEV-2670] LP:731229 - Different results depending on table access method with TIME column and CURDATE() Created: 2011-03-08  Updated: 2015-02-02  Resolved: 2012-10-04

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

Type: Bug Priority: Major
Reporter: Philip Stoev (Inactive) Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug731229.xml    

 Description   

The following query:

SELECT * FROM t1 WHERE f1 < CURDATE();

returns different results in 5.1-micro depending on the access method. FORCE KEY returns no rows while IGNORE KEY returns 2 (that is, all) rows in the table. In mysql-5.1 , both access methods return no rows.

Test case:

DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (f1 time , f2 varchar(5), KEY(f1));
INSERT INTO t1 VALUES ('00:20:01','a'),('00:20:03','b');
SELECT * FROM t1 FORCE KEY (f1) WHERE f1 < CURDATE();
SELECT * FROM t1 IGNORE KEY (f1) WHERE f1 < CURDATE();

In either version, for either access method, no warning is given even though we are comparing a DATE function to a TIME column.



 Comments   
Comment by Rasmus Johansson (Inactive) [ 2011-10-28 ]

Launchpad bug id: 731229

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