[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: |
|
| 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; 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 |