[
https://issues.apache.org/jira/browse/OPENJPA-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-893.
-------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: This is a support question, and
named parameters in native queries are still rejected by design
(params-named-in-native, persistence localizer.properties:226). The cited JPQL
FUNCTION() is wrong: JPQL.jjt has no FUNCTION token. The available workaround
is CriteriaBuilder.function (CriteriaBuilderImpl.java:496) or positional
parameters. Please reopen if this still happens with OpenJPA 4.x.
> SQLStoreQuery does not support named parameters
> ------------------------------------------------
>
> Key: OPENJPA-893
> URL: https://issues.apache.org/jira/browse/OPENJPA-893
> Project: OpenJPA
> Issue Type: Question
> Components: kernel
> Affects Versions: 1.1.0
> Environment: Weblogic 10.3, Oracle 9.2
> Reporter: Nuno Furtado
> Priority: Major
>
> I was wondering what was the reason behind this specific StoreQuery not
> allowing named parameters, and wether there was a way to get around this
> situation.
> The original problem was that the TO_DATE Oracle function was not supported
> by JPQL parser, so i was forced into a native query, and at this point i'm
> forced to redo the whole query in a somewhat troublesome way, if any of you
> can provide me with an easy solution i would appreciate it.
> Thank you in advance
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
