mariadb/mysql-test/suite/gcol
Dave Gosselin f4833ceb41 MDEV-36389 Incorrect query results for an indexed text column
Fixes a scenario where an IN subquery returned the wrong result
because the pushed WHERE clause was not retained for downstream
result filtering.  For example:
  CREATE TABLE t1 (c1 TEXT, UNIQUE (c1(1)));
  INSERT INTO t1 (c1) VALUES ('a');
  SELECT 'abc' IN (SELECT c1 FROM t1);
Internally, he 'abc' IN subquery condition becomes the constant
condition:
  'abc' = t1.c1 or t1.c1 is null
Prior to this patch, this condition was incorrectly removed when
converting the subquery engine to an index lookup-based engine.
Now eligible conditions are preserved during such engine rewrites.
2025-07-15 16:29:02 -04:00
..
inc cleanup: select ... into tests 2025-02-11 20:31:25 +01:00
r MDEV-36389 Incorrect query results for an indexed text column 2025-07-15 16:29:02 -04:00
t Merge remote-tracking branch 'github/bb-11.4-release' into bb-11.8-serg 2025-04-27 19:40:00 +02:00
disabled.def Give a reason for disabling a test 2023-09-20 08:31:28 +03:00