[Hibernate-issues] [Hibernate-JIRA] Created: (HB-209) FlushMode.AUTO problem in joined subclass hierarchy

[<leg...@at...>]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-209


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-209
    Summary: FlushMode.AUTO problem in joined subclass hierarchy
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.1

   Assignee: 
   Reporter: Panagiotis Louridas

    Created: Tue, 22 Jul 2003 8:09 AM
    Updated: Tue, 22 Jul 2003 8:09 AM
Environment: RedHat Linux 9.0, JVM 1.4.2

Description:
Suppose we have a class hierarchy 
A <- B <- C.

In my case the class hierarchy is mapped as a joined-subclass hierarchy, but my observations may hold in general.

I use a Session with the default FlushMode setting (FlushMode.AUTO). I open the session, load an object of class B or C, perform some changes on it, do some queries and flush the session. When the session is flushed, only updates for the table pertaining to class A are issued by hibernate. 

If I manually flush just before the queries hibernate performs fine, issuing the proper updates for tables B and C. The same happens when I manually flush at the end of the transaction, after the queries, but having set the Session's flush mode to FlushMode.NEVER. 


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira