diff options
author | Vicențiu Ciorbaru <cvicentiu@gmail.com> | 2023-02-15 16:20:25 +0200 |
---|---|---|
committer | Vicențiu Ciorbaru <cvicentiu@gmail.com> | 2023-02-15 16:58:31 +0200 |
commit | 4afa3b64c4e5ca12d755124befc373e0f35ff1e1 (patch) | |
tree | a5a8e853662f9120a694ee1f0a5e2ae9425e74e4 /mysql-test/main/innodb_icp.result | |
parent | d2b773d913cdcd35a727643bc16927527a5ee4bc (diff) | |
download | mariadb-git-4afa3b64c4e5ca12d755124befc373e0f35ff1e1.tar.gz |
MDEV-30324: Wrong result upon SELECT DISTINCT ... WITH TIES
WITH TIES would not take effect if SELECT DISTINCT was used in a
context where an INDEX is used to resolve the ORDER BY clause.
WITH TIES relies on the `JOIN::order` to contain the non-constant
fields to test the equality of ORDER BY fiels required for WITH TIES.
The cause of the problem was a premature removal of the `JOIN::order`
member during a DISTINCT optimization. This lead to WITH TIES code assuming
ORDER BY only contained "constant" elements.
Disable this optimization when WITH TIES is in effect.
(side-note: the order by removal does not impact any current tests, thus
it will be removed in a future version)
Reviewed by: monty@mariadb.org
Diffstat (limited to 'mysql-test/main/innodb_icp.result')
0 files changed, 0 insertions, 0 deletions