April 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2893) Criteria api does not allow a groupProperty to _NOT_ be included in the selected columns

by Antony Stubbs (JIRA)

Criteria api does not allow a groupProperty to _NOT_ be included in the selected columns ---------------------------------------------------------------------------------------- Key: HHH-2893 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2893 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: n/a Reporter: Antony Stubbs When adding a Projections.groupProperty("prop") to a criteria, the property is added to both the GROUP BY and SELECT parts of the generated SQL query. This is a major problem for using the criteria API for complex subselects that require aggregating by a column while grouping by another column. There is presently no way in the criteria API to group by a column and have it _ONLY_ in the GROUP BY clause. i.e. currently Projections.groupProperty("propOne") causes: SELECT propOne, MAX(propTwo) FROM table GROUP BY prop desired option is to have SELECT MAX(propTwo) FROM table GROUP BY prop There have been several people talking about this, but there appears to have been 'no comment'. http://forum.hibernate.org/viewtopic.php?t=939071&highlight=values+groupp... http://forum.hibernate.org/viewtopic.php?t=950803&highlight=groupproperty... http://forum.hibernate.org/viewtopic.php?t=964512&highlight=groupproperty... http://forum.hibernate.org/viewtopic.php?t=957671&highlight=groupproperty... http://forum.hibernate.org/viewtopic.php?p=2317841#2317841 http://forum.hibernate.org/viewtopic.php?t=961617&highlight=groupproperty... Find a 1st cut patch on it's way - I'm just itching my scratch now... Great work on Hibernate guys! -- 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

14 years, 10 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3325) Pagination with Oracle ROWNUM is sub-optimal

by e. wernli (JIRA)

Pagination with Oracle ROWNUM is sub-optimal -------------------------------------------- Key: HHH-3325 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3325 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Reporter: e. wernli Pagination with Oracle ROWNUM is sub-optimal The feature works but result in sub-optimal SQL. The generated SQL is the following: select * from ( select row_.*, rownum rownum_ from ( select this_.id as id3_0_, this_.version as version3_0_, this_.name as name3_0_, this_.type as type3_0_, this_.marketstatus as marketst5_3_0_ from Customer this_ order by this_.id asc ) row_ ) where rownum_ <= ? and rownum_ > ? But this SQL is faster: SELECT * FROM (SELECT row_.*, ROWNUM rownum_ FROM (SELECT this_.ID AS id3_0_, this_.VERSION AS version3_0_, this_.NAME AS name3_0_, this_.TYPE AS type3_0_, this_.marketstatus AS marketst5_3_0_ FROM customer this_ ORDER BY this_.ID ASC) row_ WHERE ROWNUM <= ?) WHERE rownum_ > ? The second solution allows Oracle to use an optimization that can dramatically reduce the time of the query, especially one of the first page is retrieved. See this link for an explanation of this optimization: http://decipherinfosys.wordpress.com/2007/08/09/paging-and-countstopkey-o... -- 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

14 years, 10 months

7
8
0 / 0

[Hibernate-JIRA] Created: (HV-461) Refactor TestUtil class

by Hardy Ferentschik (JIRA)

Refactor TestUtil class ----------------------- Key: HV-461 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-461 Project: Hibernate Validator Issue Type: Improvement Reporter: Hardy Ferentschik Priority: Minor Fix For: 4.2.0.Final Split _TestUtil_ into two classes, one related to assertions, e.g. ConstraintViolationAssert and one for setting up Validators. Also all setup and assertion methods should be checked for completeness and correctness. For example, _assertCorrectPropertyPaths_ should check the size of the property path array. -- 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

14 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4956) Native Query returns wrong results

by Akashdeep Saddi (JIRA)

Native Query returns wrong results ---------------------------------- Key: HHH-4956 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4956 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.3.2 Environment: hibernate 3.3.2.GA , linux, oracle 10g, weblogic 10 Reporter: Akashdeep Saddi Issue: In-case running native queries vai hibernate we have two technical ID's in the select clause from join of two or more tables the value of all the id's is set to one value. Example A.id = 1 B.id =2 select A.Id as A_ID, B.Id as B_ID from A, B where A.B_id = B.id will return 1,1 in the result instead of 1,2 Resolution: Use Alias in-case more than one technical keys are part of select clause. Above query works fine when changed as below select A.Id , B.Id from A, B where A.B_id = B.id will return 1,2 -- 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

14 years, 10 months

7
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2473) fetch="join" and property-ref

by David CLEMENT (JIRA)

fetch="join" and property-ref ----------------------------- Key: HHH-2473 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2473 Project: Hibernate3 Type: Improvement Versions: 3.2.1 Environment: Version 3.2.1, not DB dependant Reporter: David CLEMENT When Hibernate does a fetch join with a property-ref in a many-to-one, it issues the join SQL query but needs another select to find the associated entity by property-ref. It should be able to use the entity fetched in the join instead (maybe this has been done to ensure the unicity of the associated entity, but it introduce a performance 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

14 years, 10 months

8
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5854) ArrayIndexOutOfBounds on fetching onetoone associations using projections

by Krishna Sundaresan (JIRA)

ArrayIndexOutOfBounds on fetching onetoone associations using projections ------------------------------------------------------------------------- Key: HHH-5854 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5854 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.6.0 Environment: Hibernate version 3.6.0 Reporter: Krishna Sundaresan Attachments: testCase.zip The loading of OneToOne associations using projections results in an ArrayIndexOutOfBounds exception when the results are loaded by the CriteriaLoader. The stacktrace is: {code} Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1 at org.hibernate.loader.criteria.CriteriaLoader.getResultColumnOrRow(CriteriaLoader.java:148) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:639) at org.hibernate.loader.Loader.doQuery(Loader.java:829) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:274) at org.hibernate.loader.Loader.doList(Loader.java:2533) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2276) at org.hibernate.loader.Loader.list(Loader.java:2271) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:119) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1716) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:347) at testbed.app.HibernateApp.main(HibernateApp.java:24) Java Result: 1 {code} The problem seems to be with the way the association aliases and types are used in getResultRow. When the types are fetched, all the types that are mentioned in the projection clause are provided whereas when the aliases to be used are fetched SimpleProjection's getColumnCount method seems to be ignoring columns that do not span resulting in a mis-match of array indices. {code:title=From CriteriaLoader.getResultRow(...)} if ( translator.hasProjection() ) { Type[] types = translator.getProjectedTypes(); result = new Object[types.length]; String[] columnAliases = translator.getProjectedColumnAliases(); ... {code} The attached file has a test-case that will demonstrate the problem. Tested that on Hibernate 3.6.0 and derby. I was able to observe this in a case where the association is mapped by a shared primary key but I guess that same should be observable even without a shared primary key. -- 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

14 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6116) Envers AuditEntity.revisionProperty("...").isNotNull() creates wrong sql

by Uli Steinkopf (JIRA)

Envers AuditEntity.revisionProperty("...").isNotNull() creates wrong sql ------------------------------------------------------------------------ Key: HHH-6116 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6116 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.6.3, 3.6.2, 3.6.1, 3.6.0 Environment: hibernate 3.6.1 , oracle 10g... hibernate 3.6.3 , oracle 10g... Reporter: Uli Steinkopf Hello... AuditEntity.revisionProperty("..").isNotNull() create sql in the form of column_name <> null instead of column_name is not null like the sql standard says. E.g oracle handles "<>" different than "is not", so actual version is in this env usesless... -- 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

14 years, 10 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5718) AuditProperty.isNotNull creates an incorrect condition in the MySQL dialect

by Anthony Bishopric (JIRA)

AuditProperty.isNotNull creates an incorrect condition in the MySQL dialect --------------------------------------------------------------------------- Key: HHH-5718 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5718 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.6 Environment: 3.5.6-FINAL, MySQL 5.0.27, for apple-darwin9.3.0 Reporter: Anthony Bishopric Attachments: SampleEntity.java, SampleEntityDAO.java When using AuditProperty.isNotNull(), envers will generate a sql condition "property<>null". This condition can never evaluate to true (it must use MySQL's "is not null" convention) Attached are two example classes which should replicate 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

14 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5654) query.setLockMode("alias", LockMode.LockMode.PESSIMISTIC_WRITE); does not Lock in PostgreSqlDialect

by Peter Buning (JIRA)

query.setLockMode("alias", LockMode.LockMode.PESSIMISTIC_WRITE); does not Lock in PostgreSqlDialect --------------------------------------------------------------------------------------------------- Key: HHH-5654 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5654 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.5 Environment: Hibernate 3.5.5-Final PostgreSQL 8.4 Reporter: Peter Buning When you call {{query.setLockMode("alias", LockMode.PESSIMISTIC_WRITE);}} you get a Query with a LockOptions object that has lockMode = LockMode.NONE and a aliasSpecificLockModes-map with an entry "alias" -> LockMode.PESSIMISTIC_WRITE When calling {{query.list()}} you get to the QueryLoader which calls {{dialect.applyLocksToSql(...)}} The LockOptions-Object has still lockMode=LockMode.NONE and a aliasSpecificLockModes-map with the translated alias and -> LockMode.PESSIMISTIC_WRITE As we use PostgreSQL dialect is an instance of PostgreSQLDialect. So you get a ForUpdateFragement-object with the same LockOptions-object. The aliases-String contains the translated "alias". In {{toFragmentString()}} {{getForUpdateString(String aliases, LockOptions lockOptions)}} is called because we have a LockOptions-object. The aliases are ignored in this case, as you can see in the comment:'by default we simply return the getForUpdateString() result since the default is to say no support for "FOR UPDATE OF ..."' But the {{getForUpdateString(LockOptions lockOptions)}} is only looking at the the lockMode-Attribute of the LockOptions-object what has still the value "LockMode.NONE". It results in an empty String as the return value. But it should be " for update" because there's a LockMode.PESSIMISTIC_WRITE in the aliasSpecificLockModes which is ignored in getForUpdateString(LockOptions lockOptions) -- 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

14 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6132) Process and bind global configuration annotations

by Hardy Ferentschik (JIRA)

Process and bind global configuration annotations ------------------------------------------------- Key: HHH-6132 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6132 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- 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

14 years, 10 months

3
24
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 April 2011