You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Kevin Sutter (JIRA)" <ji...@apache.org> on 2010/09/22 00:42:32 UTC
[jira] Resolved: (OPENJPA-1582) @OrderColumn(updatable=false) may
have the order column field updated
[ https://issues.apache.org/jira/browse/OPENJPA-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter resolved OPENJPA-1582.
-----------------------------------
Assignee: Kevin Sutter
Fix Version/s: 2.0.2
2.1.0
2.0.1
2.0.0
Resolution: Not A Problem
Per Fay's remarks and a further investigation of the spec, I think this is working as designed. I'm returning the JIRA so that we can close it out.
> @OrderColumn(updatable=false) may have the order column field updated
> ---------------------------------------------------------------------
>
> Key: OPENJPA-1582
> URL: https://issues.apache.org/jira/browse/OPENJPA-1582
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.0.0-beta2
> Reporter: Albert Lee
> Assignee: Kevin Sutter
> Priority: Minor
> Fix For: 2.0.2, 2.1.0, 2.0.1, 2.0.0
>
>
> When a collection with orderColumn set updatable=false,
> @ElementCollection//(fetch=FetchType.EAGER)
> @OrderColumn(updatable=false)
> private List<String> nonUpdableAnnotatedElements;
> when collection element is updated, the order column processing performs a delete/insert sequence. The problem is that the implicit order column field is also updated while updatable=false.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.