April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Créée: (HHH-2389) Improving DB2 dialect

by Nicolas Billard (JIRA)

Improving DB2 dialect --------------------- Key: HHH-2389 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2389 Project: Hibernate3 Type: Improvement Components: query-hql Versions: 3.2.1 Environment: Development based on v 3.2.1 Reporter: Nicolas Billard Priority: Minor Attachments: DB2Dialect.java The class joined to this issue overrides the DB2 dialect. The dialect included in hibernate doesn't work very well when you want to limit returned results (when you call setFirstResult and / or setMaxResults on a query) : - the instructions "fetch first XXX row only is not used - a temporary table is used when it's not usefull - when you have subselects, an exception can occur if subselects have order by clause (because of the getRowNumber method, not corrected here). This version of getLimitString() method generates faster requests (tests made on a table of 300000 rows shows that fetching rows from 20 to 30 takes 0.3 seconds with original version, 0.02 with this one). -- 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

13 years, 4 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5007) Using <formula> within Composite Element inside Collection

by Hepoi Ko (JIRA)

Using <formula> within Composite Element inside Collection ---------------------------------------------------------- Key: HHH-5007 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5007 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5.0-CR-2 Environment: 3.5.0-CR2, AS400, Component Reporter: Hepoi Ko Priority: Minor Attachments: JoinWalker.java I was one of the user who use Hibernate in a legacy database schema, and always had a issue on using composite-key (and formula) inside collection. I was able to modify the hibernate source (from 3.3.2) to overcome such issue. I am hoping the new version 3.5.0 would even fix this problem. Anyway, I just leave the fix information here, hope it would help. In /org/hibernate/loader/JoinWalker.java Line 641: String[] aliasedLhsColumns = StringHelper.qualify(alias, lhsColumns); Modify with these: String[] fullAliasedLhsColumns = persister.getElementColumnNames(alias); String[] aliasedLhsColumns = ArrayHelper.slice(fullAliasedLhsColumns, begin, length); Without above change I would get NullPointerException on a mapping as .... <set name="auditRecords" table="OEP40A" order-by="ADAT40 DESC, ATIM40 DESC" mutable="false" inverse="true" outer-join="true"> <key> <column name="CONO40"></column> <column name="ORDN40"></column> </key> <composite-element class="com.ricoh.erp.order.domain.OrderAudit"> <property name="userId"> <column name="AUSR40"></column> </property> <property name="workstationId"> <column name="AWRK40"></column> </property> <many-to-one name="customerEntry" not-found="ignore"> <formula>CONO40</formula>  <column name="CUSN40"></column> <column name="DSEQ40"></column> </many-to-one> </composite-element> With Best Regards, -- 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

13 years, 4 months

3
15
0 / 0

[Hibernate-JIRA] Created: (HHH-4941) Log a message when an update to a mutable one-to-many collection of immutable entities is ignored

by Gail Badner (JIRA)

Log a message when an update to a mutable one-to-many collection of immutable entities is ignored ------------------------------------------------------------------------------------------------- Key: HHH-4941 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4941 Project: Hibernate Core Issue Type: Improvement Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x An update to a mutable one-to-many collection is ignored when inverse="true" and the associated entity is immutable and already exists (since it cannot be updated). Should this be a debug, info, or warning message? -- 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

13 years, 4 months

2
12
0 / 0

[Hibernate-JIRA] Created: (HHH-4760) NotAuditedException occurs when auditReader.getRevisions() is called for javassist proxies

by Erik-Berndt Scheper (JIRA)

NotAuditedException occurs when auditReader.getRevisions() is called for javassist proxies ------------------------------------------------------------------------------------------ Key: HHH-4760 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4760 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-2 Reporter: Erik-Berndt Scheper NotAuditedException occurs when auditReader.getRevisions() is called for javassist proxies In my code I see the following stacktrace if I try to retrieve the revision of a javassist proxy: org.hibernate.envers.exception.NotAuditedException: nl.ibgroep.bap.model.domain.persoon.Ouder_$$_javassist_1 is not versioned! at org.hibernate.envers.reader.AuditReaderImpl.getRevisions(AuditReaderImpl.java:126) at nl.ibgroep.bap.dao.impl.AuditRevisionJpaDaoImpl.getRevisionsFor(AuditRevisionJpaDaoImpl.java:58) Ouder_$$_javassist_1.class is a Hibernate generated javassist proxy for Ouder.class, which is versioned. Code: AuditReader vr = AuditReaderFactory.get(this.entityManager); Class clazz = persistentObject.getClass(); List<Number> revisionNumbers = vr.getRevisions(clazz, persistentObject.getId()); I am able to work around this issue with the following code: AuditReader vr = AuditReaderFactory.get(this.entityManager); Class clazz = persistentObject.getClass(); if (persistentObject instanceof javassist.util.proxy.ProxyObject) { if (LOGGER.isDebugEnabled()) { StringBuilder output = new StringBuilder("Found javassist ProxyObject for revision: class= "); output.append(clazz.getSimpleName()); output.append("; superclass= ").append(clazz.getSuperclass().getSimpleName()); output.append("; interfaces= ").append(Arrays.asList(clazz.getInterfaces()).toString()); LOGGER.debug(output.toString()); } clazz = clazz.getSuperclass(); } List<Number> revisionNumbers = vr.getRevisions(clazz, persistentObject.getId()); However, a fix in envers would be greatly appreciated. -- 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

13 years, 4 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5016) Add support for initialValue on sequence generation

by Morten Egelund Rasmussen (JIRA)

Add support for initialValue on sequence generation --------------------------------------------------- Key: HHH-5016 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5016 Project: Hibernate Core Issue Type: Improvement Reporter: Morten Egelund Rasmussen I'm having an entity with a @javax.persistence.SequenceGenerator annotation: {code} @SequenceGenerator(name = "foo.pkseq", sequenceName = "MY_SCHEME.SEQ_FOO_ID", allocationSize=1, initialValue=100) {code} I have set "hibernate.hbm2ddl.auto = create". When the sequence is created, it is created without the initialValue properly set. Referring to the documentation on Hibernate Annotations 3.4, it states that this feature is currently not implemented. I have tried with the H2 and HSQLDB databases. I'm doing some integration tests, where records are created in a RAM-based H2 or HSQLDB test database. The database is already populated with data. -- 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

13 years, 4 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-1994) Problem with case sensitive column and tables names and Identity mapping with postgreSQL

by Alex Samad (JIRA)

Problem with case sensitive column and tables names and Identity mapping with postgreSQL ---------------------------------------------------------------------------------------- Key: HHH-1994 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1994 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Hibernate 3.1.3, Java 1.5.0_07 (sun) windos and linux ( 32 & 64 bit). POstgres SQL 8.1 Windows and linux Reporter: Alex Samad Whilst trying to insert into a table with a primary key (ID mapping) which has a identity generator. And the columns and/or the table has been defined with case sensitivey ie back ticks. It fails to get the next serial number and thus fails any inserts. The problem lies in dialect/PostgreSQLDialect.java public String getIdentitySelectString(String table, String column, int type) { return new StringBuffer().append("select currval('") .append(table) .append('_') .append(column) .append("_seq')") .toString(); } table is inclosed in quotes and column is inclosed in quotes which gives a name like "table"_"Column"_seq - which fails I would suggest a fix is to test each of table or column for " and if it exist then to strip it of both of table and column and encluse the whole name in "". This mighe break some old code where say the table is coded in case insensitive table name and case sensitive column key. Sorry not much of a java programmer. -- 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

13 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5025) Support caching audit queries using ehcache's DiskStore.

by Brent Worden (JIRA)

Support caching audit queries using ehcache's DiskStore. -------------------------------------------------------- Key: HHH-5025 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5025 Project: Hibernate Core Issue Type: Improvement Components: envers Reporter: Brent Worden Priority: Minor Enabling audit query caching with a ehcache cache configured as persisting to disk or overflowing to disk. For example, <defaultCache diskPersistent="true" eternal="false" maxElementsInMemory="1000" maxElementsOnDisk="10000" overflowToDisk="true" timeToIdleSeconds="300" timeToLiveSeconds="3600" /> Results in the following exception: java.io.NotSerializableException: org.hibernate.envers.entities.RevisionTypeType at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) The lack of needed serialization prohibits the use of ehcache's DiskStore. -- 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

13 years, 4 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2655) SQLServer2005Dialect (ROW_NUMBER for Paging)

by Wells Tiedeman (JIRA)

SQLServer2005Dialect (ROW_NUMBER for Paging) -------------------------------------------- Key: HHH-2655 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2655 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.4, 3.2.3, 3.2.2 Environment: SQLServer 2005, Hibernate 3.2.2+ Reporter: Wells Tiedeman Attachments: SQLServer2005Dialect.java Add a SQLServer2005Dialect class to the product that leverages the new ROW_NUMBER capabilities within SQLServer2005 to do paged result sets more efficiently. See attached source... -- 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

13 years, 4 months

14
25
0 / 0

[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

13 years, 4 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

13 years, 4 months

7
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2010