You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/07/01 22:31:04 UTC

[jira] Assigned: (OPENJPA-274) JPQL queries cannot access version fields, including bulk updates

     [ https://issues.apache.org/jira/browse/OPENJPA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Linskey reassigned OPENJPA-274:
---------------------------------------

    Assignee: Patrick Linskey

> JPQL queries cannot access version fields, including bulk updates
> -----------------------------------------------------------------
>
>                 Key: OPENJPA-274
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-274
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc, query
>    Affects Versions: 0.9.0, 0.9.6, 0.9.7
>            Reporter: Patrick Linskey
>            Assignee: Patrick Linskey
>             Fix For: 1.0.0
>
>
> OpenJPA throws an exception if a query uses a field mapped as a @Version. This happens because FieldMappings for fields that are @Version do not have any columns, since the columns are managed separately by the owning ClassMapping's version indicator.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.