exists2in broke name resolution

Bug #884644 reported by Philip Stoev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MariaDB
Fix Released
Critical
Oleksandr "Sanja" Byelkin

Bug Description

In maria-5.3-exists2in , using tables and fields that do not exist does not cause an error:

CREATE TABLE t1 (f1 integer);
CREATE TABLE t2 (f2 integer);

SELECT * FROM t1 WHERE EXISTS (SELECT NO_SUCH_TABLE.NO_SUCH_FIELD FROM t2);
does not return an error

explain:

id select_type table type possible_keys key key_len ref rows filtered Extra
1 PRIMARY NULL NULL NULL NULL NULL NULL NULL NULL Impossible WHERE noticed after reading const tables
2 SUBQUERY t2 system NULL NULL NULL NULL 0 0.00 const row not found
Warnings:
Note 1003 select NULL AS `f1` from `test`.`t1` where 0

bzr version-info:

bzr version-info
revision-id: <email address hidden>
date: 2011-10-31 13:44:24 +0200
build-date: 2011-11-01 10:58:26 +0200
revno: 3256
branch-nick: maria-5.3-exists2in

Changed in maria:
assignee: nobody → Oleksandr "Sanja" Byelkin (sanja-byelkin)
importance: Undecided → Critical
milestone: none → 5.3
Changed in maria:
status: New → In Progress
Changed in maria:
status: In Progress → New
Changed in maria:
status: New → Fix Committed
Changed in maria:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.