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] [Updated] (DERBY-5875) Derby returns wrong results when you set the ESCAPE character to NULL in a LIKE clause.
Date Tue, 18 Sep 2012 15:52:07 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-5875:
--------------------------------------

    Labels: derby_triage10_10  (was: )
    
> Derby returns wrong results when you set the ESCAPE character to NULL in a LIKE clause.
> ---------------------------------------------------------------------------------------
>
>                 Key: DERBY-5875
>                 URL: https://issues.apache.org/jira/browse/DERBY-5875
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.10.0.0
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_10
>
> 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) )'; 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message