Menu
▾
▴
hibernate-issues
|
From: <leg...@at...> - 2003-11-09 06:27:14
|
The following comment has been added to this issue:
Author: Gavin King
Created: Sun, 9 Nov 2003 12:27 AM
Body:
fixed (finally) for load(), get() and Criteria queries .... other cases to come: HQL queries, collection initialization.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-12
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-12
Summary: low performance loading with optional 1-1 association
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:02 AM
Updated: Sat, 3 May 2003 10:02 AM
Description:
low performance loading with optional 1-1 association
I use Hibernate 1.2.3.
There is a problem, which causes a severe performance loss:
If you have 2 entites (A and B) with a 1-1 association,
Hibernate uses an SQL query with a join (if enabled) to
load both entites with 1 statement. Wonderful! If there
is a B for an A, everything is okay.
If there is no B for a certain A, Hibernate tries
(although the 1st statment returned no instance for B)
to load B, when you invoke the corresponding getter,
which results in an unnecessary SQL query!
If there are many entities associated, there are many
unnecessesary SQL queries and the performance suffers.
Thanks
Markus
(Original: http://sourceforge.net/tracker/index.php?func=detail&aid=686577&group_id=40712&atid=428708)
---------------------------------------------------------------------
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...> - 2004-04-22 13:39:24
|
The following comment has been added to this issue:
Author: CVS Notification Service
Created: Thu, 22 Apr 2004 8:45 AM
Body:
CVS COMMIT LOG:
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/loader AbstractEntityLoader.java,1.6.2.18,1.6.2.19 CollectionLoader.java,1.15.2.14,1.15.2.15 CriteriaLoader.java,1.8.2.25,1.8.2.26 EntityLoader.java,1.19.2.8,1.19.2.9 OneToManyLoader.java,1.18.2.16,1.18.2.17 OuterJoinLoader.java,1.25.2.30,1.25.2.31
apply fix for HB-12 to collection loaders
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12?page=comments#action_12914
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-12
Summary: low performance loading with optional 1-1 association
Type: Bug
Status: In Progress
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate2
Components:
core
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:02 AM
Updated: Thu, 22 Apr 2004 8:45 AM
Description:
low performance loading with optional 1-1 association
I use Hibernate 1.2.3.
There is a problem, which causes a severe performance loss:
If you have 2 entites (A and B) with a 1-1 association,
Hibernate uses an SQL query with a join (if enabled) to
load both entites with 1 statement. Wonderful! If there
is a B for an A, everything is okay.
If there is no B for a certain A, Hibernate tries
(although the 1st statment returned no instance for B)
to load B, when you invoke the corresponding getter,
which results in an unnecessary SQL query!
If there are many entities associated, there are many
unnecessesary SQL queries and the performance suffers.
Thanks
Markus
(Original: http://sourceforge.net/tracker/index.php?func=detail&aid=686577&group_id=40712&atid=428708)
---------------------------------------------------------------------
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...> - 2004-04-23 06:32:16
|
The following comment has been added to this issue:
Author: CVS Notification Service
Created: Fri, 23 Apr 2004 1:37 AM
Body:
CVS COMMIT LOG:
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/loader AbstractEntityLoader.java,1.6.2.18.2.3,1.6.2.18.2.4 CollectionLoader.java,1.15.2.13.2.3,1.15.2.13.2.4 CriteriaLoader.java,1.8.2.20.2.8,1.8.2.20.2.9 EntityLoader.java,1.19.2.8.2.2,1.19.2.8.2.3 OneToManyLoader.java,1.18.2.15.2.3,1.18.2.15.2.4 OuterJoinLoader.java,1.25.2.29.2.5,1.25.2.29.2.6
apply fix for HB-12 to collection loaders
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12?page=comments#action_12918
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-12
Summary: low performance loading with optional 1-1 association
Type: Bug
Status: In Progress
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate2
Components:
core
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:02 AM
Updated: Fri, 23 Apr 2004 1:37 AM
Description:
low performance loading with optional 1-1 association
I use Hibernate 1.2.3.
There is a problem, which causes a severe performance loss:
If you have 2 entites (A and B) with a 1-1 association,
Hibernate uses an SQL query with a join (if enabled) to
load both entites with 1 statement. Wonderful! If there
is a B for an A, everything is okay.
If there is no B for a certain A, Hibernate tries
(although the 1st statment returned no instance for B)
to load B, when you invoke the corresponding getter,
which results in an unnecessary SQL query!
If there are many entities associated, there are many
unnecessesary SQL queries and the performance suffers.
Thanks
Markus
(Original: http://sourceforge.net/tracker/index.php?func=detail&aid=686577&group_id=40712&atid=428708)
---------------------------------------------------------------------
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...> - 2004-04-23 13:30:14
|
The following comment has been added to this issue:
Author: CVS Notification Service
Created: Fri, 23 Apr 2004 8:35 AM
Body:
CVS COMMIT LOG:
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/loader AbstractEntityLoader.java,1.6.2.18.2.4,1.6.2.18.2.5 CollectionLoader.java,1.15.2.13.2.4,1.15.2.13.2.5 OneToManyLoader.java,1.18.2.15.2.4,1.18.2.15.2.5 OuterJoinLoader.java,1.25.2.29.2.7,1.25.2.29.2.8 OuterJoinableAssociation.java,1.1.2.1,1.1.2.2
more work on HB-12
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12?page=comments#action_12930
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-12
Summary: low performance loading with optional 1-1 association
Type: Bug
Status: In Progress
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate2
Components:
core
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:02 AM
Updated: Fri, 23 Apr 2004 8:35 AM
Description:
low performance loading with optional 1-1 association
I use Hibernate 1.2.3.
There is a problem, which causes a severe performance loss:
If you have 2 entites (A and B) with a 1-1 association,
Hibernate uses an SQL query with a join (if enabled) to
load both entites with 1 statement. Wonderful! If there
is a B for an A, everything is okay.
If there is no B for a certain A, Hibernate tries
(although the 1st statment returned no instance for B)
to load B, when you invoke the corresponding getter,
which results in an unnecessary SQL query!
If there are many entities associated, there are many
unnecessesary SQL queries and the performance suffers.
Thanks
Markus
(Original: http://sourceforge.net/tracker/index.php?func=detail&aid=686577&group_id=40712&atid=428708)
---------------------------------------------------------------------
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...> - 2004-04-23 15:09:13
|
The following comment has been added to this issue:
Author: CVS Notification Service
Created: Fri, 23 Apr 2004 10:14 AM
Body:
CVS COMMIT LOG:
SUBJECT: [Hibernate-commits] Hibernate2/src/net/sf/hibernate/loader AbstractEntityLoader.java,1.6.2.19,1.6.2.20 CollectionLoader.java,1.15.2.15,1.15.2.16 CriteriaLoader.java,1.8.2.26,1.8.2.27 OneToManyLoader.java,1.18.2.17,1.18.2.18 OuterJoinLoader.java,1.25.2.31,1.25.2.32
more work on HB-12
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12?page=comments#action_12931
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-12
Summary: low performance loading with optional 1-1 association
Type: Bug
Status: In Progress
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate2
Components:
core
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:02 AM
Updated: Fri, 23 Apr 2004 10:14 AM
Description:
low performance loading with optional 1-1 association
I use Hibernate 1.2.3.
There is a problem, which causes a severe performance loss:
If you have 2 entites (A and B) with a 1-1 association,
Hibernate uses an SQL query with a join (if enabled) to
load both entites with 1 statement. Wonderful! If there
is a B for an A, everything is okay.
If there is no B for a certain A, Hibernate tries
(although the 1st statment returned no instance for B)
to load B, when you invoke the corresponding getter,
which results in an unnecessary SQL query!
If there are many entities associated, there are many
unnecessesary SQL queries and the performance suffers.
Thanks
Markus
(Original: http://sourceforge.net/tracker/index.php?func=detail&aid=686577&group_id=40712&atid=428708)
---------------------------------------------------------------------
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...> - 2004-04-24 04:12:09
|
The following comment has been added to this issue:
Author: Gavin King
Created: Fri, 23 Apr 2004 11:18 PM
Body:
This is currently working for everything except <one-to-one property-ref=...> associations.
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12?page=comments#action_12935
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/HB-12
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-12
Summary: low performance loading with optional 1-1 association
Type: Bug
Status: In Progress
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate2
Components:
core
Assignee: Gavin King
Reporter: Max Rydahl Andersen
Created: Sat, 3 May 2003 10:02 AM
Updated: Fri, 23 Apr 2004 11:18 PM
Description:
low performance loading with optional 1-1 association
I use Hibernate 1.2.3.
There is a problem, which causes a severe performance loss:
If you have 2 entites (A and B) with a 1-1 association,
Hibernate uses an SQL query with a join (if enabled) to
load both entites with 1 statement. Wonderful! If there
is a B for an A, everything is okay.
If there is no B for a certain A, Hibernate tries
(although the 1st statment returned no instance for B)
to load B, when you invoke the corresponding getter,
which results in an unnecessary SQL query!
If there are many entities associated, there are many
unnecessesary SQL queries and the performance suffers.
Thanks
Markus
(Original: http://sourceforge.net/tracker/index.php?func=detail&aid=686577&group_id=40712&atid=428708)
---------------------------------------------------------------------
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