[DERBY-5875] Derby returns wrong results when you set the ESCAPE character to NULL in a LIKE clause.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.1.3.3, 10.10.1.1
• Component/s: SQL
• Labels: derby_triage10_10
• Urgency: Normal
• Issue & fix info: Repro attached
• Bug behavior facts: Deviation from standard, Wrong query result
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 23/Jul/12 13:02
• Updated: 05/Apr/13 20:07

Description

The LIKE clause is supposed to evaluate to NULL if the optional ESCAPE character is set to NULL. Instead, Derby treats this condition as equivalent to omitting the ESCAPE clause. This violates part 2 of the SQL Standard, section 8.5 <like predicate>, general rule 3.a.ii.

Thanks to Knut for disclosing this problem via the following script:

connect 'jdbc:derby:memory:db;create=true';

prepare ps as 'select tablename from sys.systables where tablename like ''SYSD%'' escape ?';

– should return no rows, but actually returns 2
execute ps using 'values cast( null as char(1) )';

Issue Links

• relates to: DERBY-5862 There is no way to escape the special _ and % characters in DatabaseMetaData search strings