[MDEV-6993] Bad results with join comparing DECIMAL and ENUM/SET columns Created: 2014-10-31 Updated: 2014-12-01 Resolved: 2014-11-19 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer |
| Affects Version/s: | 5.5.40, 10.0.14, 5.3.13 |
| Fix Version/s: | 10.0.15 |
| Type: | Bug | Priority: | Major |
| Reporter: | Alexander Barkov | Assignee: | Alexander Barkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The following three scripts comparing VARCHAR, INT and DOUBLS columns to a ENUM column correctly return 2 rows before and after adding a primary key on t2.c1.
But a DECIMAL(10,1) column does not work well in the same context:
It returns 2 rows before adding the primary key, and "empty set" after adding the key. The problem does not seem to exists in MySQL. |
| Comments |
| Comment by Alexander Barkov [ 2014-11-19 ] | |||||||||||||||||||
|
A related problem:
returns:
That is the DECIMAL column values correctly converted to ENUM values by the assignment operator. But now if I change the data type of the column "a" from DECIMAL to ENUM using ALTER TABLE, the values get lost:
returns
|