[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-5531) Version update on read-only entity fails for joined subclasses

Gail Badner (JIRA) noreply at atlassian.com
Tue Jan 11 21:32:05 EST 2011


     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gail Badner updated HHH-5531:
-----------------------------

    Summary: Version update on read-only entity fails for joined subclasses  (was: Version update fails for inherited entity classes)

> Version update on read-only entity fails for joined subclasses
> --------------------------------------------------------------
>
>                 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
>             Fix For: 3.6.1, 4.0.0.Alpha1
>
>         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