You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Catalina Wei (JIRA)" <ji...@apache.org> on 2010/07/24 18:05:50 UTC
[jira] Resolved: (OPENJPA-1738) Prepared SQL query does not handle
collection-valued parameter of persistence-capable objects
[ https://issues.apache.org/jira/browse/OPENJPA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Catalina Wei resolved OPENJPA-1738.
-----------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
> Prepared SQL query does not handle collection-valued parameter of persistence-capable objects
> ----------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1738
> URL: https://issues.apache.org/jira/browse/OPENJPA-1738
> Project: OpenJPA
> Issue Type: Bug
> Components: performance
> Affects Versions: 2.0.0, 2.0.1, 2.1.0
> Reporter: Catalina Wei
> Assignee: Catalina Wei
> Fix For: 2.1.0
>
> Attachments: OPENJPA-1738.patch
>
>
> Patrick Linskey wrote:
> I just ran into what I believe is a bug with the prepared SQL code. In PreparedQueryImpl.reparameterize(), we have the following code:
> > if (ImplHelper.isManageable(val)) {
> > setPersistenceCapableParameter(result, val, indices, broker);
> > } else if (val instanceof Collection) {
> > setCollectionValuedParameter(result, (Collection)val, indices,
> > key);
> > }
> This does not work if the parameter is a collection of persistence-capable objects, as setCollectionValuedParameter assumes that the values are not PCs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.