[
https://issues.apache.org/jira/browse/OPENJPA-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728998#action_12728998
]
Michael Dick commented on OPENJPA-1169:
---------------------------------------
Sounds like a good idea. In hindsight we should have added such a property
(Compatibility class) earlier I guess.
Jianfeng, can you illustrate the problem without U2JPA?
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
