[MDEV-27101] Subquery using the ALL keyword on TIMESTAMP columns produces a wrong result Created: 2021-11-20 Updated: 2022-11-01 Resolved: 2022-08-22 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data types |
| Affects Version/s: | 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8 |
| Fix Version/s: | 10.9.2, 10.10.1, 10.4.27, 10.5.18, 10.6.10, 10.7.6, 10.8.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Alexander Barkov | Assignee: | Alexander Barkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Description |
|
This bug is related to To reproduce this bug, make sure the time zone information is loaded, e.g.:
I create a table with a TIMESTAMP column and insert to values near DST change:
It returns the following result:
Now I run a query with an ALL subquery:
The result is wrong. The query is expected to return only the smallest value - the first record. Now I run a different query with an ALL subquery:
The result is wrong. The query is expected to return only the greatest value - the second record. |