[DERBY-1231] LIKE does not match empty strings when used with a prepared statement

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.2.2.0, 10.3.1.4
• Component/s: JDBC, SQL
• Urgency: Normal
• Assignee: Bernt Johnsen
• Reporter: Dyre Tjeldvoll
• Created: 20/Apr/06 18:02
• Updated: 13/Dec/07 09:04
• Resolved: 06/Dec/06 11:46

Description

LIKE should give true for two 0-length strings. See SQL 2003 Ch. 8.5
General Rules 3)c)i)

The query SELECT * FROM t WHERE v like ''

appears to give me all rows where v is an empty
string, as expected.

But a prepared statement

SELECT * FROM t WHERE v like ?, with setString(1, "")

always returns an empty result set. See attached repro for the full example.

Issue Links

• blocks: DERBY-2145 Remove LIKE tweak from metadata.properties
• is part of: DERBY-2034 Tracking of bugs that lead to incorrect results being stored or returned to the client
• is related to: DERBY-1386 Wrong results with query using LIKE and ESCAPE clause that includes "%", "\", and "_"