[MDEV-2792] LP:884644 - exists2in broke name resolution Created: 2011-11-01  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Philip Stoev (Inactive) Assignee: Oleksandr Byelkin
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug884644.xml    

 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



 Comments   
Comment by Rasmus Johansson (Inactive) [ 2011-12-13 ]

Launchpad bug id: 884644

Generated at Thu Feb 08 06:44:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.