January 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-1211) FetchMode.SELECT not working on criteria queries

by Jon Lorusso (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1211?page=c... ] Jon Lorusso commented on HHH-1211: ---------------------------------- Almost 5 years and the documentation is still wrong. I wonder how many have been tripped up by this? > FetchMode.SELECT not working on criteria queries > ------------------------------------------------ > > Key: HHH-1211 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1211 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5, HSQLDB 1.8.0.1 > Reporter: Heiko Briebrecher > Attachments: FetchModeTest.java > > > Lazy associations are not eagerly fetched when FetchMode.SELECT is set on Criteria Queries (see attached Testcase). -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4820) @IdClass with "extra" attributes leads to misleading error

by Steve Ebersole (JIRA)

@IdClass with "extra" attributes leads to misleading error ---------------------------------------------------------- Key: HHH-4820 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4820 Project: Hibernate Core Issue Type: Bug Reporter: Steve Ebersole Assignee: Hardy Ferentschik Even if we end up not supporting HHH-4819, the error message we currently give is completely wrong. The error message names some non-@Id annotated field in the entity class even though it is the field in the pk class that causes the issue. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4819) Hibernate errors when @IdClass class contains "extra" attributes

by Steve Ebersole (JIRA)

Hibernate errors when @IdClass class contains "extra" attributes ---------------------------------------------------------------- Key: HHH-4819 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4819 Project: Hibernate Core Issue Type: Bug Components: annotations Reporter: Steve Ebersole This is based on an interpretation of wording in the spec. What the spec says is: {quote} If the composite primary key class is represented as an id class, the names of primary key fields or properties in the primary key class and those of the entity class to which the id class is mapped must correspond and their types must be the same {quote} So imagine an entity such as {code} @Entity @IdClass(MyEntityPK.class} class MyEntity { @Id Long id1; @Id Long id2; ... } {code} and {code} class SimplePK implements Serializable { private final Long id1; private final Long id2; private final transient int cachedHashCode; public SimplePK(Long id1, Long id2) { this.id1 = id1; this.id2 = id2; this.cachedHashCode = calculateHashCode(); } private int calculateHashCode() { ... } @Override public int hashCode() { return cachedHashCode; } ... } {code} This is valid according to the spec. The entity has 2 attributes marked with @Id. The "pk class" has 2 attributes that match the types and names of those attributes perfectly as specified by the spec. -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4818) Do not require @IdClass class to have no-arg constructor

by Steve Ebersole (JIRA)

Do not require @IdClass class to have no-arg constructor -------------------------------------------------------- Key: HHH-4818 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4818 Project: Hibernate Core Issue Type: Improvement Components: annotations Reporter: Steve Ebersole Drop the requirement that @IdClass class have a no-arg constructor; we do not instantiate these things, ever! -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-448) Update JPATestCase after renaming of HibernatePersistence to AvailableSettings in Core

by Hardy Ferentschik (JIRA)

Update JPATestCase after renaming of HibernatePersistence to AvailableSettings in Core -------------------------------------------------------------------------------------- Key: HSEARCH-448 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-448 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0.Beta2 -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3338) Order of attributes in generated SQL query is dependent on Java version

by Michael Gerz (JIRA)

Order of attributes in generated SQL query is dependent on Java version ----------------------------------------------------------------------- Key: HHH-3338 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3338 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: WIndows XP, Java 5 Update 15, Java 6 update 5 Reporter: Michael Gerz We use Hibernate Core 3.2.6 in combination with Derby 10.4.1.3. When migrating from Java 5 to Java 6, we noticed a huge performance hit. Our analysis has unveiled that Hibernate 3.2.6 produces semantical identical but syntactically different queries for Java 5 and Java 6. Java 5: Hibernate: select logevent0_.ID as ID7_, logevent0_.INDEX_SENT as INDEX2_7_, logevent0_.TEST_RUN_ID as TEST3_7_, logevent0_.SENDER as SENDER7_, logevent0_.TIME_SENT as TIME5_7_, logevent0_.MESSAGE as MESSAGE8_, logevent0_.SEVERITY as SEVERITY8_, logevent0_.SERIALIZED_CONTENT as SERIALIZED1_11_, logevent0_.RECEIVER as RECEIVER11_, logevent0_.TIME_RECEIVED as TIME3_11_, logevent0_.INDEX_RECEIVED as INDEX4_11_, logevent0_.ACTION_REQUEST as ACTION1_13_, logevent0_.ACTION_REPLY as ACTION1_14_, logevent0_.clazz_ as clazz_ from ( select TEST_RUN_ID, SENDER, MESSAGE, SEVERITY, nullif('x','x') as SERIALIZED_CONTENT, nullif('2000-1-1 00:00:00','2000-1-1 00:00:00') as TIME_RECEIVED, ID, nullif('x','x') as ACTION_REQUEST, TIME_SENT, nullif('x','x') as ACTION_REPLY, nullif('x','x') as RECEIVER, nullif(0,0) as INDEX_RECEIVED, INDEX_SENT, 2 as clazz_ from USER_LOG_EVENT union all select TEST_RUN_ID, SENDER, MESSAGE, SEVERITY, nullif('x','x') as SERIALIZED_CONTENT, nullif('2000-1-1 00:00:00','2000-1-1 00:00:00') as TIME_RECEIVED, ID, nullif('x','x') as ACTION_REQUEST, TIME_SENT, nullif('x','x') as ACTION_REPLY, nullif('x','x') as RECEIVER, nullif(0,0) as INDEX_RECEIVED, INDEX_SENT, 3 as clazz_ from DEVEL_LOG_EVENT union all select TEST_RUN_ID, SENDER, nullif('x','x') as MESSAGE, nullif('x','x') as SEVERITY, nullif('x','x') as SERIALIZED_CONTENT, nullif('2000-1-1 00:00:00','2000-1-1 00:00:00') as TIME_RECEIVED, ID, ACTION_REQUEST, TIME_SENT, nullif('x','x') as ACTION_REPLY, nullif('x','x') as RECEIVER, nullif(0,0) as INDEX_RECEIVED, INDEX_SENT, 6 as clazz_ from ACTION_REQUEST_LOG_EVENT union all select TEST_RUN_ID, SENDER, nullif('x','x') as MESSAGE, nullif('x','x') as SEVERITY, nullif('x','x') as SERIALIZED_CONTENT, nullif('2000-1-1 00:00:00','2000-1-1 00:00:00') as TIME_RECEIVED, ID, nullif('x','x') as ACTION_REQUEST, TIME_SENT, ACTION_REPLY, nullif('x','x') as RECEIVER, nullif(0,0) as INDEX_RECEIVED, INDEX_SENT, 7 as clazz_ from ACTION_REPLY_LOG_EVENT union all select TEST_RUN_ID, SENDER, nullif('x','x') as MESSAGE, nullif('x','x') as SEVERITY, SERIALIZED_CONTENT, TIME_RECEIVED, ID, nullif('x','x') as ACTION_REQUEST, TIME_SENT, nullif('x','x') as ACTION_REPLY, RECEIVER, INDEX_RECEIVED, INDEX_SENT, 4 as clazz_ from DATA_FLOW_LOG_EVENT ) logevent0_ where logevent0_.TEST_RUN_ID=? Java 6: Hibernate: select logevent0_.ID as ID7_, logevent0_.INDEX_SENT as INDEX2_7_, logevent0_.TEST_RUN_ID as TEST3_7_, logevent0_.SENDER as SENDER7_, logevent0_.TIME_SENT as TIME5_7_, logevent0_.MESSAGE as MESSAGE8_, logevent0_.SEVERITY as SEVERITY8_, logevent0_.SERIALIZED_CONTENT as SERIALIZED1_11_, logevent0_.RECEIVER as RECEIVER11_, logevent0_.TIME_RECEIVED as TIME3_11_, logevent0_.INDEX_RECEIVED as INDEX4_11_, logevent0_.ACTION_REQUEST as ACTION1_13_, logevent0_.ACTION_REPLY as ACTION1_14_, logevent0_.clazz_ as clazz_ from ( select nullif('x','x') as RECEIVER, TIME_SENT, SEVERITY, nullif('2000-1-1 00:00:00','2000-1-1 00:00:00') as TIME_RECEIVED, ID, SENDER, MESSAGE, TEST_RUN_ID, nullif('x','x') as SERIALIZED_CONTENT, INDEX_SENT, nullif(0,0) as INDEX_RECEIVED, nullif('x','x') as ACTION_REQUEST, nullif('x','x') as ACTION_REPLY, 2 as clazz_ from USER_LOG_EVENT union all select nullif('x','x') as RECEIVER, TIME_SENT, SEVERITY, nullif('2000-1-1 00:00:00','2000-1-1 00:00:00') as TIME_RECEIVED, ID, SENDER, MESSAGE, TEST_RUN_ID, nullif('x','x') as SERIALIZED_CONTENT, INDEX_SENT, nullif(0,0) as INDEX_RECEIVED, nullif('x','x') as ACTION_REQUEST, nullif('x','x') as ACTION_REPLY, 3 as clazz_ from DEVEL_LOG_EVENT union all select nullif('x','x') as RECEIVER, TIME_SENT, nullif('x','x') as SEVERITY, nullif('2000-1-1 00:00:00','2000-1-1 00:00:00') as TIME_RECEIVED, ID, SENDER, nullif('x','x') as MESSAGE, TEST_RUN_ID, nullif('x','x') as SERIALIZED_CONTENT, INDEX_SENT, nullif(0,0) as INDEX_RECEIVED, ACTION_REQUEST, nullif('x','x') as ACTION_REPLY, 6 as clazz_ from ACTION_REQUEST_LOG_EVENT union all select nullif('x','x') as RECEIVER, TIME_SENT, nullif('x','x') as SEVERITY, nullif('2000-1-1 00:00:00','2000-1-1 00:00:00') as TIME_RECEIVED, ID, SENDER, nullif('x','x') as MESSAGE, TEST_RUN_ID, nullif('x','x') as SERIALIZED_CONTENT, INDEX_SENT, nullif(0,0) as INDEX_RECEIVED, nullif('x','x') as ACTION_REQUEST, ACTION_REPLY, 7 as clazz_ from ACTION_REPLY_LOG_EVENT union all select RECEIVER, TIME_SENT, nullif('x','x') as SEVERITY, TIME_RECEIVED, ID, SENDER, nullif('x','x') as MESSAGE, TEST_RUN_ID, SERIALIZED_CONTENT, INDEX_SENT, INDEX_RECEIVED, nullif('x','x') as ACTION_REQUEST, nullif('x','x') as ACTION_REPLY, 4 as clazz_ from DATA_FLOW_LOG_EVENT ) logevent0_ where logevent0_.TEST_RUN_ID=? The first order (using Java 5) looks more reasonable, because TEST_RUN_ID is the first column in all of the tables and it is also a foreign key. The changed order of attributes does not really explain why Derby performs so poor on Java 6 and we have already issued a report to the Derby community. Nevertheless, the SQL queries generated Hibernate should not depend on a specific version of Java. Maybe a compareTo() method is missing somewhere in the code...? -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

5
11
0 / 0

[Hibernate-JIRA] Created: (HHH-4669) Implement JDBC driver properties support

by Emmanuel Bernard (JIRA)

Implement JDBC driver properties support ---------------------------------------- Key: HHH-4669 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4669 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4816) Cleanup JPA setting name constants

by Steve Ebersole (JIRA)

Cleanup JPA setting name constants ---------------------------------- Key: HHH-4816 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4816 Project: Hibernate Core Issue Type: Improvement Components: entity-manager Reporter: Steve Ebersole Fix For: 3.5.0-Beta-4 -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4793) Revert disabling of VersionsJoinTableRangeComponentNamingTest and fix underlying issue

by Steve Ebersole (JIRA)

Revert disabling of VersionsJoinTableRangeComponentNamingTest and fix underlying issue -------------------------------------------------------------------------------------- Key: HHH-4793 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4793 Project: Hibernate Core Issue Type: Task Components: envers Affects Versions: 3.5.0-Beta-3 Reporter: Steve Ebersole Assignee: Adam Warski Fix For: 3.5.0-Beta-4 See HHH-4790 -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4726) Add support for delete-orphan cascading to <one-to-one/>

by Steve Ebersole (JIRA)

Add support for delete-orphan cascading to <one-to-one/> -------------------------------------------------------- Key: HHH-4726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4726 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Steve Ebersole Fix For: 3.5 JPA 2 requires support for this. See section "11.1.37 OneToOne Annotation" wrt the orphanRemoval attribute -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2010