[
https://issues.apache.org/jira/browse/OPENJPA-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049237#comment-13049237
]
Pinaki Poddar commented on OPENJPA-1999:
----------------------------------------
The commit shows no tests with PreparedQuery. In a related thread, it had been
discussed that a change of this nature *may* impact PreparedQuery.
How about executing few of the queries with non-kosher binding parameter twice
so that the second time the parameters get rebind?
> Optional support for non-sequential positional parameters
> ---------------------------------------------------------
>
> Key: OPENJPA-1999
> URL: https://issues.apache.org/jira/browse/OPENJPA-1999
> Project: OpenJPA
> Issue Type: Improvement
> Components: competitive, jpa, query, usability
> Reporter: David Blevins
> Assignee: Rick Curtis
> Fix For: 2.2.0
>
> Attachments: OPENJPA-1999.patch
>
>
> Optional support for less strict following of positional parameters. e.g.
> Query query = entityManager.createQuery("SELECT m from Movie as m WHERE
> m.title = ?2 AND m.year = ?4");
> query.setParameter(2, "Foo");
> query.setParameter(4, 2011);
> return query.getResultList();
> Previous OpenJPA releases support this as do current EclipseLink and
> Hibernate versions. For the migration and upgrade scenarios and the
> development scenario -- can be a pain to have to always update positional
> parameters while tweaking queries -- this could make a compelling optional
> feature.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
