Menu
▾
▴
hibernate-issues
|
From: <leg...@at...> - 2003-07-22 14:58:02
|
The following comment has been added to this issue:
Author: Panagiotis Louridas
Created: Tue, 22 Jul 2003 9:57 AM
Body:
FlushMode.AUTO works OK if before flushing at the end of the transaction a Session.save(anotherObject) operation is performed; hibernate then issues the correct UPDATE statements just after the INSERT statement for anotherObject.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-22 16:07:05
|
The following comment has been added to this issue:
Author: Panagiotis Louridas
Created: Tue, 22 Jul 2003 11:06 AM
Body:
After changing hibernate's log level to DEBUG I see some of the subclasses' fields as dirty. It then seems that whenever, after marking these fields as dirty, hibernate outputs that "Dont need to execute flush" and leaves it for later on, when the time comes it has forgotten the subclasses' fields.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-23 01:03:01
|
The following comment has been added to this issue:
Author: Gavin King
Created: Tue, 22 Jul 2003 8:02 PM
Body:
I'm quite skeptical about this one, and certainly you will need to submit a test case to help me reproduce it.
Submit the test as a _very_ simple main() method that isolates the problem.
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-07-29 16:16:14
|
The following comment has been added to this issue:
Author: Panagiotis Louridas
Created: Tue, 29 Jul 2003 11:15 AM
Body:
Will you be uploading the patch to public CVS? (I am getting a 11 days old SessionImpl).
Cheers,
Panos.
---------------------------------------------------------------------
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: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.0.2
Versions:
2.0.1
Assignee: Gavin King
Reporter: Panagiotis Louridas
Created: Tue, 22 Jul 2003 8:09 AM
Updated: Sun, 27 Jul 2003 7:34 PM
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
|
|
From: <leg...@at...> - 2003-07-30 15:54:14
|
The following comment has been added to this issue:
Author: Panagiotis Louridas
Created: Wed, 30 Jul 2003 10:53 AM
Body:
It works fine!
Thanks!
---------------------------------------------------------------------
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: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.0.2
Versions:
2.0.1
Assignee: Gavin King
Reporter: Panagiotis Louridas
Created: Tue, 22 Jul 2003 8:09 AM
Updated: Sun, 27 Jul 2003 7:34 PM
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
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X