[
https://issues.apache.org/jira/browse/OPENJPA-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Catalina Wei updated OPENJPA-1388:
----------------------------------
Affects Version/s: (was: 2.0.0)
1.3.0
Summary: JPQL named parameter using a reserved word resulting in
ArgumentException (was: JPQL named parameter using a reserved word (:vlaue)
resulting in ArgumentException)
Same fix applied to 1.3 branch
> 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: 2.0.0
>
>
> 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.
