[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5531) Version update fails for inherited entity classes
Gail Badner (JIRA)
noreply at atlassian.com
Mon Jan 10 19:09:05 EST 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39542#action_39542 ]
Gail Badner commented on HHH-5531:
----------------------------------
This looks like a bug.
You should be able to add/remove entities from a unidirectional association, even if the owner is read-only.
> Version update fails for inherited entity classes
> -------------------------------------------------
>
> Key: HHH-5531
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5531
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.5.5, 3.6.0.Beta4
> Environment: MySql 5.1.37-1 (ubuntu)
> Reporter: Tobias Bergman
> Assignee: Gail Badner
> Attachments: hibernate-inheritance-bug.zip
>
>
> When adding an item to a collection for which the owner is fetched as READ_ONLY the version update fails if the owner class has a parent class (with a join strategy), but without parent it works.
> The problem is that the AbstractEntityPersister.getTableUpdateNeeded() returns with getTableHasColumns() (line 2748) when the owner is fetch as READ_ONLY. For a single table this probably works by luck.
> But what is the correct behavior? Should it be possible to update an READ_ONLY fetched owner's collection?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list