db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement
Date Wed, 06 Dec 2006 09:26:22 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1231?page=all ]

Bernt M. Johnsen updated DERBY-1231:
------------------------------------

    Attachment: DERBY-1231-v3.diff

Thanks Knut. Here's the final patch

> 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-v2.diff, DERBY-1231-v3.diff, 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

        

Mime
View raw message