May 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2380) Hibernate3.2.0 GA is JDK 1.3 Incompatible

by Alessandro Lazarotti (JIRA)

Hibernate3.2.0 GA is JDK 1.3 Incompatible ----------------------------------------- Key: HHH-2380 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2380 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: Hibernate 3.2.0 GA Reporter: Alessandro Lazarotti Priority: Minor The class org.hibernate.persister.entity.AbstractEntityPersister uses Boolean.valueOf, incompatible with JDK 1.3. Update for new Boolean. -- 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, 2 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2295) entity-name attribute's syntax not clearly documented

by Jeremy Michael Crosbie (JIRA)

entity-name attribute's syntax not clearly documented ----------------------------------------------------- Key: HHH-2295 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2295 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.1 Environment: Windows XP/JDK 1.5/HypersonicSQL Reporter: Jeremy Michael Crosbie Priority: Minor Attachments: Group.hbm.xml Setting entity-name to a value containing a hyphen, in my case 'lender-group' causes odd behaviors seemingly only when calling get() or load(). Also in my case I am mapping a class to two different tables (attached). The first mapping has an entity name with a hyphen, the other does not. When I call load *after committing a transaction where a new entity is persisted* I get an exception (see below). The exception complains of a column called "LENDER" not existing. But once I change the entity-name to something like 'lendergroup' the problem goes away. Interestingly, the missing column complained about is the text before the hyphen, so if I name the entity 'lndr-group' it complains of a column name 'LNDR' not existing. It almost appears if this format is assuming some sort of discriminator, but the online docs are terse when it comes to describing the entity-name field. Exception: org.hibernate.exception.SQLGrammarException: could not load an entity: [lender-group#G9] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.loadEntity(Loader.java:1799) 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:177) 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 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.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:301) at $Proxy0.get(Unknown Source) at com.fares.mtrac.group.GroupDaoImpl.findById(GroupDaoImpl.java:148) at com.fares.mtrac.group.GroupDaoImplTest.testFindByIdStringCompanyType(GroupDaoImplTest.java:256) 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 junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) 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:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.sql.SQLException: Column not found: LENDER in statement [select lender-gro0_.group_cd as group1_48_0_, lender-gro0_.group_nm as group2_48_0_, lender-gro0_.user_nm as user3_48_0_ from lender_group_name lender-gro0_ where lender-gro0_.group_cd=?] at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.<init>(Unknown Source) at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:442) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:368) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:105) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1561) at org.hibernate.loader.Loader.doQuery(Loader.java:661) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) ... 36 more -- 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, 2 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2088) TypeMismatchException on object equality expression from one-to-one relationship

by Salvatore Insalaco (JIRA)

TypeMismatchException on object equality expression from one-to-one relationship -------------------------------------------------------------------------------- Key: HHH-2088 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2088 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Reporter: Salvatore Insalaco Suppose to have entity A with a one-to-one constrained relationship to an entity B, called bRel. The query: "from A a, B b where a.bRel = b" raises a TypeMismatchException, even if bRel and b are instances of the same entity. This happens because in BinaryLogicOperatorNode: - lhsType is org.hibernate.type.Type = org.hibernate.type.OneToOneType(B)", with getColumnSpan returning 0. - rhsType is org.hibernate.type.Type = org.hibernate.type.ManyToOneType(B)", with getColumnSpan returning 1. And it compares the two columnspans. It doesn't happen with 3.2.0.cr2. -- 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, 3 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2341) ObjectNotFoundException on session.get() on non-existent object

by Timo Thomas (JIRA)

ObjectNotFoundException on session.get() on non-existent object --------------------------------------------------------------- Key: HHH-2341 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2341 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: HSQLDB 1.8.0 Reporter: Timo Thomas Hibernate version: 3.2.1 GA (same for hibernate-annotations) Mapping documents: Parent.java (omitting package and some import declarations) import javax.persistence.*; @Entity public class Parent { public Integer id; public Set<Child> children = new HashSet<Child>(); @Id @GeneratedValue(strategy = GenerationType.AUTO) public Integer getId() { return id; } public void setId(Integer id) { this.id = id; } @OneToMany(mappedBy = "parent", cascade = CascadeType.ALL) public Set<Child> getChildren() { return children; } public void setChildren(Set<Child> children) { this.children = children; } } Child.java (omitting package and some import declarations) import javax.persistence.*; @Entity public class Child { public Integer id; public Parent parent; @Id @GeneratedValue(strategy = GenerationType.AUTO) public Integer getId() { return id; } public void setId(Integer id) { this.id = id; } @ManyToOne(optional = false) @JoinColumn(name = "parent_fk") public Parent getParent() { return parent; } public void setParent(Parent parent) { this.parent = parent; } } Code between sessionFactory.openSession() and session.close(): Transaction transaction = session.beginTransaction(); Parent parent = new Parent(); parent.setName("p1"); session.persist(parent); assertNotNull(parent.getId()); Integer parentId = parent.getId(); Child child = new Child(); child.setName("c1"); child.setParent(parent); parent.getChildren().add(child); session.persist(parent); assertNotNull(child.getId()); Integer childId = child.getId(); transaction.commit(); session.close(); /////////////////////////////////////////// session = sessionFactory.openSession(); transaction = session.beginTransaction(); parent = (Parent) session.load(Parent.class, parentId); child = (Child) session.load(Child.class, childId); // child = (Child) session.get(Child.class, childId); session.delete(parent); // session.flush(); // !! required if session&transaction is re-opened and child is obtained with load(), otherwise exception on next line - BUG ? child = (Child) session.get(Child.class, childId); Full stack trace of any exception that occurs: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [model.Child#1] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:375) at org.hibernate.event.def.DefaultLoadEventListener.returnNarrowedProxy(DefaultLoadEventListener.java:223) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:187) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:815) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:808) at test.CascadeAnnotationTest.testBug(CascadeAnnotationTest.java:48) 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 junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:228) at junit.framework.TestSuite.run(TestSuite.java:223) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) The generated SQL (show_sql=true): Hibernate: insert into Parent (id, name) values (null, ?) Hibernate: call identity() Hibernate: insert into Child (id, name, parent_fk) values (null, ?, ?) Hibernate: call identity() Hibernate: select parent0_.id as id0_0_, parent0_.name as name0_0_ from Parent parent0_ where parent0_.id=? Hibernate: select children0_.parent_fk as parent3_1_, children0_.id as id1_, children0_.id as id1_0_, children0_.name as name1_0_, children0_.parent_fk as parent3_1_0_ from Child children0_ where children0_.parent_fk=? Why is this exception thrown under these circumstances? Am I using the API in an undocumented/disallowed way? If yes, where exactly? The Hibernate API doc says, that Session.get() returns null if an object can't be found. No exception should be thrown. However, Session.get() at the end of sample code does return null as expected, if either a) Session.get() is used instead of load() some lines above (see commented line) b) the transaction and the session is isn't closed or reopened, respectively c) Session.flush() is called before the final call to Session.get() I'd like to understand why Hibernate behaves like this, which I presume is erroneous. I'm a beginner in Hibernate, but I couldn't get any help in the forum. Timo -- 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, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2575) Query results are mapped to object array incorrectly when there is column ambiguity and aliases are not used

by Mike Hoeffner (JIRA)

Query results are mapped to object array incorrectly when there is column ambiguity and aliases are not used ------------------------------------------------------------------------------------------------------------ Key: HHH-2575 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2575 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.2 Environment: Hibernate 3.2.2 + MySQL 5.0.22 + MySQL Connector/J 5.0.5. Reproduced with HSQLDB 1.8.0.7. Reporter: Mike Hoeffner Priority: Minor Attachments: ResultsNotEffectedByAliasesTest.java I had a SQL (not HQL) query that basically looked like this: select a.name, a.seq, b.name, b.seq from foo a, foo b; and I noticed that the results obtained through list() -> (Object[]) get(i) -> row[0], row[1], row[2], row[3] did not correspond to what I saw when manually running the query without Hibernate involved. row[2] always had the same values as row[0] and row[3] always had the same values as row[1]. When I tried adding aliases so that it became: select a.name as a_name, a.seq as a_seq, b.name as b_name, b.seq as b_seq from foo a, foo b; then the results matched what I expected. So having aliases in the SQL modified the results that were returned even though I was looking up the value from each column by its index / position instead of by its name / alias. Attached is a test case that will reproduce this. -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-507) @Digits(integerDigits, fractionalDigits)

by Emmanuel Bernard (JIRA)

@Digits(integerDigits, fractionalDigits) ---------------------------------------- Key: ANN-507 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-507 Project: Hibernate Annotations Type: New Feature Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.2 @Digits(integerDigits=8, fractionalDigits=2) ensure that the number can be expressed with integerDigits digits and factionalDigits digits -- 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, 3 months

6
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2047) make Query and Criteria extend java.lang.Iterable

by Amir Pashazadeh (JIRA)

make Query and Criteria extend java.lang.Iterable ------------------------------------------------- Key: HHH-2047 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2047 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.cr2 Reporter: Amir Pashazadeh Priority: Trivial Objects which implement java.lang.Iterable can be iterated using extended for loop. -- 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, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-407) <synchronize table="table_name"/> is missed using annotations

by Amir Pashazadeh (JIRA)

<synchronize table="table_name"/> is missed using annotations -------------------------------------------------------------- Key: ANN-407 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-407 Project: Hibernate Annotations Type: Patch Components: binder Versions: 3.2.0.cr1 Reporter: Amir Pashazadeh in old .hbm.xml notation there was a possibility to set a synchronize for caches on particular tables, and I could not find such thing using annotations, is it possible to set "synchronize" tables using annotations? and if not will it be added to 3.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, 4 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-53) Add support for projection (ie read the data from the index only)

by Emmanuel Bernard (JIRA)

Add support for projection (ie read the data from the index only) ----------------------------------------------------------------- Key: HSEARCH-53 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-53 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.0.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

14 years, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-1985) NodeTraverser is not SOE-safe

by Sergey Vladimirov (JIRA)

NodeTraverser is not SOE-safe ----------------------------- Key: HHH-1985 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1985 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.cr3 Reporter: Sergey Vladimirov Priority: Minor org.hibernate.hql.ast.util.NodeTraverser It is possible for java.lang.StackOverflowError to occur in NodeTraverser.java:41;42 with very deep tree. Need another algorith to visit whole tree. 08.08 19:50:09 ERROR [ArpSiteServlet] Servlet.service() for servlet ArpSiteServlet threw exception java.lang.StackOverflowError at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:41) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:41) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) at org.hibernate.hql.ast.util.NodeTraverser.visitDepthFirst(NodeTraverser.java:42) -- 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, 4 months

7
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2007