[MCOL-1382] Incorrect results returned when comparing incompatible columns in the where clause Created: 2018-05-03 Updated: 2022-11-05 Resolved: 2022-11-05 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ExeMgr |
| Affects Version/s: | 1.1.4 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Epic Link: | ColumnStore Compatibility Improvements |
| Description |
|
Build tested: 1.1.4-1 For the following query, MariaDB server returned: MariaDB [mytest]> select dtt1.cidx, dtt1.CVCHAR8, dtt2.CDATETIME from datatypetestm1 dtt1, datatypetestm2 dtt2 where dtt1.cidx = dtt2.cidx and dtt1.CVCHAR8 < dtt2.CDATETIME
-----
----- MariaDB [mytest]> show warnings;
--------
-------- it seems that it tried to cast the vchar8 column values to date time. In this case it, actually returned results. ColumnStore did not return any rows. if the > operator is used, server returned no results while ColumnStore did. This is reported by the Autopilot/datatypecasting test suite. 52 test cases did not pass and they all have DATE/DATETIME columns involved in the comparison. |
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2018-05-04 ] |
|
It will get the datetime values from dtt2, cast those as CHAR and then compare. Although it doesn't look like it is even doing that correctly as inverting the WHERE condition (dtt1.CVCHAR8 < dtt2.CDATETIME) also produces no results. |
| Comment by Todd Stoffel (Inactive) [ 2022-11-05 ] |
|
This item is being closed because it was well passed the expiration date with no activity. If you suspect this was done in error please create a new ticket. |