[ http://issues.apache.org/jira/browse/DERBY-1231?page=comments#action_12455551 ] Dyre Tjeldvoll commented on DERBY-1231: ---------------------------------------
Thanks for looking at this Bernt! :) Patch looks good to me. +1 to commit. Wrt, your question above: Yes, I think the tweak in metadata.properties was to added as a workaround for this bug. It was added in revision 395414 which was Rick Hillegas' checkin of the work I did on DERBY-925. I'll let you figure out if it is safe to change metadata.properties now, or if that could cause problems during upgrade, (will you ever use the new metadata.properties with the old code that has the bug? Does it matter if a metadata query returns the wrong results in that situation?). > LIKE does not match empty strings when used with a prepared statement > --------------------------------------------------------------------- > > Key: DERBY-1231 > URL: http://issues.apache.org/jira/browse/DERBY-1231 > Project: Derby > Issue Type: Bug > Components: JDBC, SQL > Affects Versions: 10.1.2.1, 10.1.3.1, 10.3.0.0, 10.2.1.6 > Reporter: Dyre Tjeldvoll > Assigned To: Bernt M. Johnsen > Fix For: 10.2.2.0 > > Attachments: DERBY-1231.diff, vti.java > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
