db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement
Date Tue, 05 Dec 2006 10:04:24 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1231?page=comments#action_12455563 ] 
Knut Anders Hatlen commented on DERBY-1231:

Dyre wrote:
> I'll let you figure out if it is safe to change metadata.properties now, or if that could
cause problems during upgrade

It is safe to make this change to metadata.properties on trunk. However, it is not safe to
make this change on the 10.2 branch. If one creates a database with Derby 10.2.X.Y which includes
that change, the query will not work correctly if one moves back to which doesn't
include the change.

> 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:,,,
>            Reporter: Dyre Tjeldvoll
>         Assigned To: Bernt M. Johnsen
>             Fix For:
>         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


View raw message