[
https://issues.apache.org/jira/browse/OPENJPA-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-1169.
--------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: The fix aa2934297 exists only on
origin/1.3.x, a line that was never released. On master,
AbstractQuery.setParameter(int) declares any position for native queries
(AbstractQuery.java:167-169), and SQLStoreQuery.toParameterArray
(SQLStoreQuery.java:345-366) maps ?n tokens to user params, so gaps are
allowed. Please reopen if this still happens with OpenJPA 4.x.
> OpenJPA 1.3.0's query parameter checking is too restricitive for native
> queries that used to work with OpenJPA 1.2.x
> --------------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1169
> URL: https://issues.apache.org/jira/browse/OPENJPA-1169
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.3.0
> Environment: Windows XP
> Reporter: Jianfeng Mao
> Priority: Major
>
> OpenJPA 1.3.0's new query positional parameter handling are a lot stricter
> than 1.2.x and causes U2JPA queries that can have arbitrary number of
> input/output parameters to fail. A solution is suggested by Pinaki Poddar to
> introduce a property that specifies a ParameterIndexingStyle to restore the
> 1.2.x behavior for U2JPA but keep its compatibility with the current OpenJPA
> core.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
