October 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2025) Remove log from LazyInitializationException constructor

by Russell Healy (JIRA)

Remove log from LazyInitializationException constructor ------------------------------------------------------- Key: HHH-2025 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2025 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.1 Environment: Any Reporter: Russell Healy Remove log from LazyInitializationException constructor. The motivation is to enable recovery from a LazyInitializationException using around advice without issuing a logging an error. See: http://www.jroller.com/page/cenkcivici?entry=reattaching_lazy_objects_to_... This has been asked for before [HB-1363], but is worth reconsidering. -- 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

18 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2010) getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected.

by Lari Hotari (JIRA)

getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected. --------------------------------------------------------------------------------------- Key: HHH-2010 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2010 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3, 3.2.0.cr3 Environment: 3.1.3, DB2 Reporter: Lari Hotari The correct getForUpdateString for DB2 should be "for update with rr" see: http://opensource.atlassian.com/projects/hibernate/browse/HB-1032 DB2 will release all locks created in a result set if the isolation level is lower than TRANSACTION_SERIALIZABLE (RR in DB2). Locks and concurrency control in DB2: http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.do... " The duration of row locking varies with the isolation level being used: * UR scans: No row locks are held unless row data is changing. * CS scans: Row locks are only held while the cursor is positioned on the row. * RS scans: Only qualifying row locks are held for the duration of the transaction. * RR scans: All row locks are held for the duration of the transaction. " -- 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

18 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2116) CLONE -explicit and implicit query with enabled filter gives different results

by Armin Haaf (JIRA)

CLONE -explicit and implicit query with enabled filter gives different results ------------------------------------------------------------------------------ Key: HHH-2116 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2116 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: hibernate 3.2.0.cr2, hibernate annotations 3.2.0.cr1 Reporter: Armin Haaf we are playing around with filters and found a inconsistent behaviour in using a filter in an explicit vs. implicit join. In explicit join a filter is not active, but in an implicit join it is active. Please look at the attachment -- 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

18 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2104) Infinite recursion in org.hibernate.cfg.Configuration.setListener(String, Object)

by Daniel Beer (JIRA)

Infinite recursion in org.hibernate.cfg.Configuration.setListener(String, Object) --------------------------------------------------------------------------------- Key: HHH-2104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2104 Project: Hibernate3 Type: Bug Components: core Versions: 3.1 rc 1 Environment: Hibernate 3.1, but also newer versions contain this bug. Reporter: Daniel Beer When method org.hibernate.cfg.Configuration.setListener(String, Object) is called with second argument set to <null> (in order to remove all listeners of that type) an infinite recursion occurs. Cause: There is a check against null in this method which invokes a wrong method (its a simple typos): if ( listener == null ) { setListener( type, null ); } Instead the method "setListeners(String, Object[])" should be invoked (notice the trailing "s" in the methods name). -- 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

18 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-1991) add alias when create a subcriteria

by Jorge L. Middleton (JIRA)

add alias when create a subcriteria ----------------------------------- Key: HHH-1991 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1991 Project: Hibernate3 Type: Improvement Components: query-criteria Versions: 3.1 rc2 Environment: windows Reporter: Jorge L. Middleton Priority: Trivial Its very simple... only I noted this: public DetachedCriteria createCriteria(String associationPath, String alias) throws HibernateException { return new DetachedCriteria( impl, criteria.createCriteria(associationPath) ); } I had a problem with this method because, hibernate doesn't recognize the alias. The point is that you have to use criteria.createCriteria(associationPath, alias); -- 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

18 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2022) ORA-00911: invalid character when field begins with underscore

by Jerry Cattell (JIRA)

ORA-00911: invalid character when field begins with underscore -------------------------------------------------------------- Key: HHH-2022 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2022 Project: Hibernate3 Type: Bug Components: core Versions: 3.0.5, 3.1.3, 3.2.0.cr3 Environment: Hibernate 3.1.3 Oracle 10.2.0.1 Reporter: Jerry Cattell Priority: Minor Attachments: InvalidCharacterErrorCase.java, SimpleObject.hbm.xml, SimpleObject.java Hibernate is generating invalid SQL (for Oracle) for collections that are stored in fields with names that start with underscores. In this SQL: Hibernate: select _tags0_.SIMPLE_OBJECT_ID as SIMPLE1_0_, _tags0_.TAG as TAG0_ from SIMPLE_OBJECT_TAG _tags0_ where _tags0_.SIMPLE_OBJECT_ID=? an alias called "_tags0_" is created for the collection table. Unfortunately, Oracle does not allow non-alphabetic characters for the first character in an alias. Here's the stacktrace: Hibernate: select _tags0_.SIMPLE_OBJECT_ID as SIMPLE1_0_, _tags0_.TAG as TAG0_ from SIMPLE_OBJECT_TAG _tags0_ where _tags0_.SIMPLE_OBJECT_ID=? WARN JDBCExceptionReporter 20060822-011120.817 - SQL Error: 911, SQLState: 42000 ERROR JDBCExceptionReporter 20060822-011120.818 - ORA-00911: invalid character INFO DefaultLoadEventListener 20060822-011120.820 - Error performing load command org.hibernate.exception.SQLGrammarException: could not initialize a collection: [SimpleObject._tags#1] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.loadCollection(Loader.java:1926) at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:36) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1676) at org.hibernate.collection.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:454) at org.hibernate.engine.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:755) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:229) at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:47) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:41) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2730) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:365) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:346) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:161) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:862) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:799) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:792) at InvalidCharacterErrorCase.runTest(InvalidCharacterErrorCase.java:28) at InvalidCharacterErrorCase.main(InvalidCharacterErrorCase.java:11) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Caused by: java.sql.SQLException: ORA-00911: invalid character at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:799) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:839) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1132) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3329) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139) at org.hibernate.loader.Loader.getResultSet(Loader.java:1669) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.loadCollection(Loader.java:1919) ... 26 more I have attached a test case that causes this error. After a little bit of research, it appears that a change to StringHelper.generateAlias(String description, int unique) (or StringHelper.generateAliasRoot(String description)) to remove all characters up to the first alphabetic character would solve this problem. -- 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

18 years

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2156) Section 19.3, "Managing the caches" doesn't document CacheMode.IGNORE

by Anders Wallgren (JIRA)

Section 19.3, "Managing the caches" doesn't document CacheMode.IGNORE --------------------------------------------------------------------- Key: HHH-2156 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2156 Project: Hibernate3 Type: Bug Components: metamodel Versions: 3.2.0.ga Reporter: Anders Wallgren CacheMode.IGNORE is used in other sections, but is not documented in Section 19.3, along with the other CacheModes. -- 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

18 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2189) Left Outer Join Conditions

by yann degat (JIRA)

Left Outer Join Conditions -------------------------- Key: HHH-2189 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2189 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.1.3 Reporter: yann degat Priority: Blocker Attachments: OracleJoinFragment.java, OracleJoinFragment.java the "org.hibernate.sql.OracleJoinFragment.addLeftOuterJoinCondition" does not take the "!=" operator into account. it places the "(+)" like this "!(+)=" instead of " (+) !=" ( != is a valid operator for Oracle ) and it returns (+)<(+)> for the '<>' operator here's a patch. (maybe not the best one ) /** * This method is a bit of a hack, and assumes * that the column on the "right" side of the * join appears on the "left" side of the * operator, which is extremely wierd if this * was a normal join condition, but is natural * for a filter. */ private void addLeftOuterJoinCondition(String on) { StringBuffer buf = new StringBuffer( on ); for ( int i = 0; i < buf.length(); i++ ) { char character = buf.charAt( i ); boolean isInsertPoint = OPERATORS.contains( new Character( character ) ) || ( character == ' ' && buf.length() > i + 3 && "is ".equals( buf.substring( i + 1, i + 4 ) ) ) ; if( character == '<' && buf.length() > i + 1 && ">".equals( buf.substring( i + 1, i + 2 ) ) ){ isInsertPoint = false; buf.insert( i, "(+)" ); i += 3 + 2; } if ( isInsertPoint ) { buf.insert( i, "(+)" ); i += 3; } if( character == '!' && buf.length() > i + 1 && "=".equals( buf.substring( i + 1, i + 2 ) ) ){ buf.insert( i, "(+)" ); i += 3 + 2; } } addCondition( buf.toString() ); } -- 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

18 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2106) * criteria queries

by Toby (JIRA)

* criteria queries ------------------ Key: HHH-2106 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2106 Project: Hibernate3 Type: New Feature Components: query-criteria Reporter: Toby -localArea -wideArea - country Imagine you want to query local area that belong to a country, independet of the "wide area". But country is only references via a wide area and there is no direct link between local area and a country. You can not add wide area as a restriction as the problem ist, that you want all wide areas....and you only need them to get to the county..... Criteria c = session.createCriteria(LocalArea.class); c.add(Restrictions.eq("wideArea", *)); c.add(Restrictions.eq("country", country)); -- 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

18 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2164) Minor bug in section "20.1.1. Customizing the schema"

by Andres Gonzalez (JIRA)

Minor bug in section "20.1.1. Customizing the schema" ----------------------------------------------------- Key: HHH-2164 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2164 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0.ga Reporter: Andres Gonzalez Where it says: ******************************************************************************************************************************* A unique-key attribute may be used to group columns in a single unique key constraint. Currently, the specified value of the unique-key attribute is not used to name the constraint in the generated DDL, only to group the columns in the mapping file. <many-to-one name="org" column="orgId" unique-key="OrgEmployeeId"/> <property name="employeeId" unique-key="OrgEmployee"/> ******************************************************************************************************************************* i think the unique-key attributes should jave both the same value ("OrgEmployee", for example) -- 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

18 years, 1 month

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2006