You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2010/02/24 15:02:27 UTC

[jira] Updated: (OPENJPA-1388) JPQL named parameter using a reserved word resulting in ArgumentException

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

Donald Woods updated OPENJPA-1388:
----------------------------------

    Fix Version/s:     (was: 2.0.0)
                   2.0.0-beta

> JPQL named parameter using a reserved word resulting in ArgumentException
> -------------------------------------------------------------------------
>
>                 Key: OPENJPA-1388
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1388
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 1.3.0
>            Reporter: Catalina Wei
>            Assignee: Catalina Wei
>             Fix For: 1.3.0, 2.0.0-beta
>
>
> In JPA2, additional reserved words are introduced in the JPQL language. For example,  KEY, VALUE, ENTRY, CASE, etc.
> These keywords is causing existing application that migrate to JPA2 regressed in ArgumentException (JPQL parser error).
> For example,
>      JPQL:  select c from Customer c where c.name = :value
> :value is a named parameter, but 'value' is a reserved word in JPA2.
> The above query used to work in OpenJPA-1.2.x but not in OpenJPA-2.x

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.