db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5629) Queries with guarded null Parameter fail
Date Fri, 23 Mar 2012 18:45:30 GMT

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

Rick Hillegas updated DERBY-5629:

    Urgency: Normal  (was: Urgent)

Hi Bernard,

Looking at Kristian, Knut, and Dag's comments, I get the impression that this is not legal
syntax in the Standard dialect which Derby supports. The fix would be for Hibernate to generate
ANSI/ISO Standard syntax when the datastore is Derby.

I have lowered the urgency of this issue. The Urgency field is owned by the release manager.
It reflects the release manager's judgment about the issues which gate the next release. You
are welcome to adjust the Priority field to reflect how important this issue is to you.

> Queries with guarded null Parameter fail
> ----------------------------------------
>                 Key: DERBY-5629
>                 URL: https://issues.apache.org/jira/browse/DERBY-5629
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions:
>         Environment: java version "1.6.0_30"
> Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
> Java HotSpot(TM) Client VM (build 20.5-b03, mixed mode, sharing)
>            Reporter: Bernard
>              Labels: derby_triage10_9
>         Attachments: NullParameterHibernateDerbyMaven.zip, NullParameterHibernateHsqlMaven.zip
> Some test cases in the attached Maven project fail where a null parameter is passed in
or a null value is coded in the query.
> In the context of this issue, a recently closed issue appears to be relevant:
> "Add support for setObject(<arg>, null)"
> https://issues.apache.org/jira/browse/DERBY-1938
> Some test cases in the attached project are Hibernate JPQL cases where Hibernate takes
care of generating the SQL queries.
> I thought it was appropriate to make a few cases not only one so that the issue gets
a little more test coverage.
> I also assume that issue DERBY-1938 aims to fix what we can see in these cases.
> This has become a major issue because it causes failure of a minimalistic JPQL query
as shown at
> http://en.wikipedia.org/wiki/Java_Persistence_Query_Language#Examples
> that shows a JPQL query:
> SELECT a FROM Author a WHERE :lastName IS NULL OR LOWER(a.lastName) = :lastName

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message