December 2006 - hibernate-issues - Jboss List Archives

by Urban.Lindberg＠tietoenator.com

Hi I believe I just discovered little bug in Hibernate 3.2.1. If you have a table named VC and a column with the same name (VC) and you define this HQL: Strinh hbsql="update VC set timestamp='xxxx' where VC =:vcId" session.createQuery(hbsql).setString("vcId", aVC.getVcId()).executeUpdate(); You will get a Nullpointer in SessionFactoryHelper.findSQLFunction there is a easy workaround, just rename the VC java object to something different then the column name. I post it here and maybe someone wll be helped by it, it took me some hours before I found it. I believe this occured in 3.2.1 because it has worked in an erlier version, 3.0.x. (don't rember exactly which we used earlier) Here is a trace: java.lang.NullPointerException at org.hibernate.hql.ast.util.SessionFactoryHelper.findSQLFunction(SessionF actoryHelper.java:342) at org.hibernate.hql.ast.tree.IdentNode.getDataType(IdentNode.java:266) at org.hibernate.hql.ast.tree.BinaryLogicOperatorNode.extractDataType(Binar yLogicOperatorNode.java:168) at org.hibernate.hql.ast.tree.BinaryLogicOperatorNode.initialize(BinaryLogi cOperatorNode.java:34) at org.hibernate.hql.ast.HqlSqlWalker.prepareLogicOperator(HqlSqlWalker.jav a:1006) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker .java:3992) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.ja va:1762) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.ja va:1690) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.ja va:1687) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.ja va:776) at org.hibernate.hql.antlr.HqlSqlBaseWalker.updateStatement(HqlSqlBaseWalke r.java:358) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java :237) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.ja va:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl. java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.ja va:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache .java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionIm pl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.j ava:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) at com.teliasonera.wal.inventory.atmpvc.dao.SybaseATMPVCDAO.updateVC(Sybase ATMPVCDAO.java:398) at com.teliasonera.wal.inventory.atmpvc.ATMPVCHandler.updateVC(ATMPVCHandle r.java:203) at com.teliasonera.wal.inventory.atmpvc.ATMPVCHandler.updateVC(ATMPVCHandle r.java:197) at com.teliasonera.wal.inventory.atmpvc.ATMPVCHandlerTest.testUpdateVC(ATMP VCHandlerTest.java:164) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUn it3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.ja va:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe stRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe stRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRun ner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRu nner.java:196)

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-381) Make possible to specify an @EmbeddedId's field in a @OneToMany's mappedBy property

by Paul Kuit (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-381?page=co... ] Paul Kuit commented on ANN-381: ------------------------------- Works Excellent! > Make possible to specify an @EmbeddedId's field in a @OneToMany's mappedBy property > ----------------------------------------------------------------------------------- > > Key: ANN-381 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-381 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Environment: Hibernate's annotations packaged in JBoss EJB 3.0 RC8- FD > Microsoft SQL Server 2000 > Reporter: Pierre Fourès > Fix For: 3.2.0.cr2 > > > As described in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=960763) and discussed with Emmanuel, it would be very nice to be able to specify in an @OneToMany's mappedBy property the field of an @EmbeddedId. > For example, i would like to be able run this example : > @Entity > public class Card { > @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER, mappedBy="primaryKey.card") > private Set<CardField> fields; > } > @Entity > public class CardField implements Field { > @EmbeddedId > private PrimaryKey primaryKey = new PrimaryKey(); > > @Embeddable > class PrimaryKey implements Serializable { > @ManyToOne(optional = false) > private Card card; > > @ManyToOne(optional = false) > private Key key; > } > } > @Entity > public class 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

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2313) Please Help me: The Perfomance of Hibernate3 Query is very poor, Special in multi thread

by wang.chungang (JIRA)

Please Help me: The Perfomance of Hibernate3 Query is very poor, Special in multi thread ---------------------------------------------------------------------------------------- Key: HHH-2313 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2313 Project: Hibernate3 Type: Bug Versions: 3.1.3 Environment: Hibernate 3.1.3+MySQL5.1+Tomcat Reporter: wang.chungang Attachments: Noname2.txt Where using Hibernate3 as my P-O layer, I had found the performance of Query is very poor, special in multi thread.what can i do? I just see The All Thread is waiting soming, The Attachment is my execute logs. My Code is: String sHql = "from "+UzionDocumentPhoto.class.getName()+" WHERE publictype=:iPublicType ORDER BY id desc"; Session session = null; try{ System.out.println(Thread.currentThread()+":start open session["+System.currentTimeMillis()+"]"); session = HibernateUtil.openSession(); System.out.println(Thread.currentThread()+":End open session["+System.currentTimeMillis()+"]"); Query query = session.createQuery(sHql); query.setInteger("iPublicType", IPhotoConstants.PHOTO_PUBLICTYPE_PUBLIC); query.setFirstResult(iStart); if(iSize>0) query.setMaxResults(iSize); System.out.println(Thread.currentThread()+":Before Execute["+System.currentTimeMillis()+"]"); List retList = query.list(); System.out.println(Thread.currentThread()+":End Execute["+System.currentTimeMillis()+"]"); return retList; } catch(Exception ex){ throw ex; } finally{ HibernateUtil.closeSession(session); } -- 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

17 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2043) There is an bug in InformixDialect preventing generator-class=native to work.

by Andrew from Poland (JIRA)

There is an bug in InformixDialect preventing generator-class=native to work. ----------------------------------------------------------------------------- Key: HHH-2043 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2043 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3, 3.2.0.cr4 Environment: hibernate version 3.1.3, IBM Informix Dynamic Server Version 10.00.FC3R1, JDBC IBM Informix driver ver 3.0.JC3 (ifxjdbc-3.0-jc3.jar) Reporter: Andrew from Poland Priority: Minor When there is an column of SERIAL or SERIAL8 type (identity types in Informix) database expect this column to appear in INSERT clause with value equal 0, for example: INSERT into my_table (my_serial_column, other_column) values (0, "some value"); - in this example my_serial_column is an identity column. Using current InformixDialect this insert looks like this: INSERT into my_table (other_column) values ( "some value"); which causes an exception: java.sql.SQLException: Error In Specifying Automatically (Server) Generated Keys. at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:373) at com.informix.jdbc.IfxSqli.a(IfxSqli.java:3208) at com.informix.jdbc.IfxSqli.E(IfxSqli.java:3518) at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2353) at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2269) at com.informix.jdbc.IfxSqli.executePrepare(IfxSqli.java:1153) at com.informix.jdbc.IfxPreparedStatement.e(IfxPreparedStatement.java:318) at com.informix.jdbc.IfxPreparedStatement.a(IfxPreparedStatement.java:298) at com.informix.jdbc.IfxPreparedStatement.<init>(IfxPreparedStatement.java:275) at com.informix.jdbc.IfxSqliConnect.prepareStatement(IfxSqliConnect.java:2077) at org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:418) at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(PoolingDataSource.java:385) 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 org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:40) at $Proxy10.prepareStatement(Unknown Source) ... I've tested a solution - dialect must redefine getIdentityInsertString method like this: public String getIdentityInsertString() { return "0"; } After that identity column appear in INSERT clause with value set to 0. I'am using hibernate version 3.1.3, but in the latest build 3.2.0.cr4 problem still exist (i've downloaded it and checked InformixDialect.java file). -- 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

17 years, 6 months

4
4
0 / 0

[Hibernate-JIRA] Commented: (HHH-1512) Problem to lock a row in a DB2 database with LockMode UPGRADE

by Milosz Tylenda (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1512?page=c... ] Milosz Tylenda commented on HHH-1512: ------------------------------------- I run the tests using current SVN snapshot and DB2 9.1. Actually JPALockTest hangs up in both testLockModeTypeRead and testLockModeTypeWrite methods when run on DB2 - no matter which of 1-7 statements we choose. Even if we remove all for update/read only/with stuff from SELECTs, the test still hangs. This is because DB2 locks rows "aggressively" - after transaction 1 have updated a row, transaction 2 tries to select this row and hangs until transaction 1 commits/rolls back. That is the case even if transactions use Cursor Stability (=JDBC's Read Committed) isolation level. I opened two command line clients, switched auto-commit off and checked which phenomena statements 1-7 prevent. The results are as follows: 1) prevents dirty reads, concurrent writes, concurrent reads 2) prevents dirty reads, concurrent writes, concurrent reads 3) prevents only uncommitted reads 4) prevents dirty reads, concurrent writes 5) prevents dirty reads, concurrent writes, concurrent reads 6) prevents dirty reads, concurrent writes, concurrent reads 7) prevents dirty reads, concurrent writes, concurrent reads (even if the concurrent transaction uses select without update/read only/with clause) It seems that if we want to prevent only dirty reads and concurrent writes, the current DB2Dialect is OK. If we also want to prevent concurrent reads, we should use one of 1, 2, 5, 6, 7. Maybe it can make Hibernate more portable across databases. > Problem to lock a row in a DB2 database with LockMode UPGRADE > ------------------------------------------------------------- > > Key: HHH-1512 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1512 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Environment: DB2 v8.2, Hibernate 3.1 and higher > Reporter: Peter Potthoff > Assignee: Steve Ebersole > Attachments: locks.txt > > Original Estimate: 1 hour > Remaining: 1 hour > > Using the LockMode UPGRADE to lock a row in the database, this will result in > a sql-statement: select ID from <schema>.<table> where ID =? and version =? for read only with rs > This statement produces a shared lock and cannot be used for pessimistic locking because > this kind of lock won't stop a concurrent thread from accessing the data. > The source of the class DB2Dialect.java was changed from release 1.34 to 1.35: > http://cvs.sourceforge.net/viewcvs.py/hibernate/Hibernate3/src/org/hibern... > and from 1.33 to 1.34 > http://cvs.sourceforge.net/viewcvs.py/hibernate/Hibernate3/src/org/hibern... > Please take a look at: HHH-378 and http://forum.hibernate.org/viewtopic.php?t=954639&highlight=db2+lock+upgrade -- 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

17 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2312) criteria with annotation mapping leads to bad join on a 1:n:n relation

by Sebastian Hennebrueder (JIRA)

criteria with annotation mapping leads to bad join on a 1:n:n relation ---------------------------------------------------------------------- Key: HHH-2312 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2312 Project: Hibernate3 Type: Bug Versions: 3.2.1 Environment: Ubuntu Linux PostgreSQL 8.0 database Reporter: Sebastian Hennebrueder Attachments: HibernateTest.zip I have a 1:n to 1:n relation, ie. Forest has many Trees has many Leafs. I try to select all Trees having a leaf which name is test. session.createCriteria(Tree.class).createCriteria("leafs").add(Restrictions.eq("name", "test")).list(); If I use XML mapping, I receive a proper query: select this_.id as id1_1_, leaf1_.id as id0_0_, leaf1_.name as name0_0_, leaf1_.tree_id as tree3_0_0_ from tree this_ inner join leaf leaf1_ on this_.id=leaf1_.tree_id where leaf1_.name=? but if I use annotation mapping, I get a very ugly join returning not even the correct values: select this_.id as id2_3_, this_.forest_id as forest2_2_3_, leaf1_.id as id0_0_, leaf1_.tree_id as tree3_0_0_, leaf1_.name as name0_0_, tree4_.id as id2_1_, tree4_.forest_id as forest2_2_1_, forest5_.id as id1_2_ from Tree this_ inner join Leaf leaf1_ on this_.id=leaf1_.tree_id left outer join Tree tree4_ on leaf1_.tree_id=tree4_.id left outer join Forest forest5_ on tree4_.forest_id=forest5_.id where leaf1_.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

17 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2231) Using "create table" strictly from org.hibernate.dialect.Dialect

by Mark Gorokhov (JIRA)

Using "create table" strictly from org.hibernate.dialect.Dialect ---------------------------------------------------------------- Key: HHH-2231 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2231 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.ga Environment: Hibernate v 3.2.0, October 16, 2006, HSQLDB 1.8.0.7 (Using In-process mode) Reporter: Mark Gorokhov Priority: Trivial Configuration property setProperty(Environment.HBM2DDL_AUTO, "update") automatically create missing HSQLDB In-process database. HSQL default "create table" is converted to "create memory table". Hibernate does not provide an option to convert "create table" into "create cached table". A keyword "create table" could be found in Hibernate core in many places, including org.hibernate.mapping.Table without an option to override "create table" behavior. Proposed: add method Dialect.getCreateTableString() similar to to Dialect.getCreateTemporaryTableString() and use it everywere in the code where "create table" is required. -- 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

17 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1646) Bad code in FastClass.equals

by Scott Marlow (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1646?page=c... ] Scott Marlow commented on HHH-1646: ----------------------------------- Fix also checked into Branch_3_2 revision 10998. > Bad code in FastClass.equals > ---------------------------- > > Key: HHH-1646 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1646 > Project: Hibernate3 > Type: Bug > Versions: 3.1.3, 3.2.0 cr1 > Environment: 3.2.0 > Reporter: Niels Harremoës > Assignee: Scott Marlow > Priority: Blocker > Fix For: 3.2.2 > Attachments: FastClass.patch > > Original Estimate: 30 minutes > Remaining: 30 minutes > > In FastClass, the equals method is: > public boolean equals(Object o) { > if ( o == null || ( o instanceof FastClass ) ) { > return false; > } > return this.type.equals( ( ( FastClass ) o ).type ); > } > There's a missing ! - the first line should be > if ( o == null || ! ( o instanceof FastClass ) ) { -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2311) SessionFactoryImpl.close: exceptions thrown while destroying caches can cause ConnectionProvider not to be closed.

by Frank Grimes (JIRA)

SessionFactoryImpl.close: exceptions thrown while destroying caches can cause ConnectionProvider not to be closed. ------------------------------------------------------------------------------------------------------------------ Key: HHH-2311 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2311 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate-3.2.1, JBoss-4.0.5.GA, EHCache-1.2.4 Reporter: Frank Grimes The following problem with EHCache-1.2.4 has highlighted what I believe to be a weakness in Hibernate's Exception handling in SessionFactoryImpl.close: http://sourceforge.net/tracker/index.php?func=detail&aid=1616492&group_id... For reference, this was also brought up on the following Hibernate forums entry: http://forum.hibernate.org/viewtopic.php?t=968632 -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1915) DerbyDialect javadoc

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1915?page=c... ] Steve Ebersole commented on HHH-1915: ------------------------------------- Because our test suite shows problems running against Derby using IDENTITY columns. It almost as if in certain circumstances the just inserted IDENTITY value is not available when performing a later FK check in the same transaction. For example, in the same connection/transaction, the following paradigm fails often: insert into Employee (id) values (default) {generatedEmployeeId} = values identity_val_local() insert into Employer (id) values (default) {generatedEmployerId} = values identity_val_local() insert into EMPLOYER_EMPLOYEE (EMPER_ID, EMPEE_ID) values ( {generatedEmployerId}, {generatedEmployeeId} ) this last insert fails with an FK constraint violation. This happens whether we make the "values identity_val_local()" call seperately or whether we use getGeneratedKeys(). > DerbyDialect javadoc > -------------------- > > Key: HHH-1915 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1915 > Project: Hibernate3 > Type: Improvement > Components: documentation > Versions: 3.1.2 > Environment: Hibernate 3.1.2, Derby 10.1.2.1 > Reporter: Brian Bonner > > > Hibernate 3.1.2's DerbyDialect seems to work around some issues in Derby's JDBC 3.0 Support, but it's not clearly documented in the Javadoc why it is the case. > For example: > Derby does support Identity columns (http://db.apache.org/derby/docs/10.1/ref/rrefidentityvallocal.html) and it looks like the Dialect includes this, but then it uses the TableHiLoGenerator instead of the IdentityGenerator. > I assume it's to work around this problem: > http://forum.hibernate.org/viewtopic.php?t=951233&highlight=derby+native > but I can't say for certain. > I've created a JIRA on Derby: https://issues.apache.org/jira/browse/DERBY-1518 for the preparedStatement issue highlighted here, with the assumption that this is the reason. -- 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

17 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2006