April 2007 - hibernate-issues - Jboss List Archives

[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, 9 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, 10 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, 10 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, 10 months

3
3
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, 11 months

7
9
0 / 0

[Hibernate-JIRA] Created: (HBX-869) SchemaUpdateTask does not actually APPLY the DDL on Mysql 5.0

by Schwark Satyavolu (JIRA)

SchemaUpdateTask does not actually APPLY the DDL on Mysql 5.0 ------------------------------------------------------------- Key: HBX-869 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-869 Project: Hibernate Tools Type: Bug Components: ant Versions: 3.2beta9 Environment: Mysql 5.0, windows Reporter: Schwark Satyavolu Priority: Critical The ant task in verbose mode shows that the table does not exist, prints the ddl for the create table, but in fact does NOT create the table. Yet, the build is reported successful. -- 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, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2288) Adding a new ResultTransformer, permitting to instantiate and fill related beans and not to take care of aliases case.

by Nicolas Billard (JIRA)

Adding a new ResultTransformer, permitting to instantiate and fill related beans and not to take care of aliases case. ---------------------------------------------------------------------------------------------------------------------- Key: HHH-2288 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2288 Project: Hibernate3 Type: Improvement Components: query-sql, query-hql, query-criteria Versions: 3.2.1 Environment: Developped based on hibernate v 3.2.1 Reporter: Nicolas Billard Priority: Minor Attachments: ResultTransformerImprovement.zip Are joined to this post 2 classes. Below is the javadoc header of the ResultTransformer class. May be this could be integrated in next hibernate versions ( certainly with improvements ... :p ) Let me know if anyone finds it useful ... ------------------------------------------------------ * Transforms resultset to value a bean, via setters. * * Examples: * * bean MyBean as 2 setters : * - setId : takes an Integer * - setProduct : takes a Product bean * * Product bean as 2 setters : * - setId * - setLib * * resultset may have these columns : * - ID * - PRODUCT_ID * - PRODUCT_LIB * * A MyBean instance will be created for each tupple, * and a Product instance will be also created, filled with PRODUCT_ID and PRODUCT_LIB values. -- 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, 11 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2501) Read-only state of an entity in a session to propagate into subsequently lazy-loaded entities.

by Gunther Schadow (JIRA)

Read-only state of an entity in a session to propagate into subsequently lazy-loaded entities. ---------------------------------------------------------------------------------------------- Key: HHH-2501 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2501 Project: Hibernate3 Type: Improvement Components: core Environment: any Reporter: Gunther Schadow ISSUE: Given an Entity entity and after Session.setReadOnly(entity), if the entity has lazy collections, lazy properties etc., other Entities are loaded into the Session upon navigating the object graph in the default read-writable state. However, it seems more reasonable to maintain the read-only state of the owning object. REQUEST: Ability to propagate read-only state of an entity in a session into other lazy-loaded entities. BACKGROUND: We have a system which permits users to make concurrent transactions which involve many of the same objects. Usually no changes happen on these shared objects, but instead connections (links) are made between these objects and new objects. For example, say you have an online meeting system, and every Meeting held has a link to a number of User object. The User objects are never changed in a Meeting, but there is a Relation called Participation (of User in Meeting) to which new relationships are added. When a new meeting is saved, it wants to save the User objects simply because a new Participation link entry was added to the collection. To an extent we can prevent this from happening by setting the Users explicitly to read-only. However, now suppose we added a function "Invite your Friends" to a Meeting, in which we would simply go: for(User friend : currentUser.getFriends()) meeting.addInvitation(friend); Now an Invitation is like a Participation, and would be added into the User but now it wants to save these users just for a version upgrade only because they have received an Invitation. -- 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, 11 months

5
13
0 / 0

[Hibernate-JIRA] Created: (HHH-2094) Hibernate is ignoring native sql aliases and generating "column not found" error

by Leonardo Penczek (JIRA)

Hibernate is ignoring native sql aliases and generating "column not found" error -------------------------------------------------------------------------------- Key: HHH-2094 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2094 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.2.0.cr4 Environment: 3.2.0.cr4, Adaptive Server Enterprise/12.5.3 Reporter: Leonardo Penczek Priority: Critical As simples as that: 1: Query q = em.createNativeQuery("select cd_person as codePerson, cd_person as identif from PERSON"); 2: List<Object[]> resultList = (List<Object[]>) q.getResultList(); Hibernate is ignoring my aliases when retrieving information from the ResultSet because it is trying to retrieve by column name, generating the following error: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:641) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:73) at <my line 2 in the code above> ... Caused by: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2147) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2028) at org.hibernate.loader.Loader.list(Loader.java:2023) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:289) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1695) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:150) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:64) ... Caused by: java.sql.SQLException: S0022: Invalid column name 'cd_person'. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source) at com.sybase.jdbc3.tds.TdsResultSet.findColumnByLabel(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.findColumn(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getInt(Unknown Source) at org.jboss.resource.adapter.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:690) at org.hibernate.type.IntegerType.get(IntegerType.java:28) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:113) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:139) at org.hibernate.loader.custom.CustomLoader$ScalarResultColumnProcessor.extract(CustomLoader.java:474) at org.hibernate.loader.custom.CustomLoader$ResultRowProcessor.buildResultRow(CustomLoader.java:420) at org.hibernate.loader.custom.CustomLoader.getResultColumnOrRow(CustomLoader.java:317) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:594) at org.hibernate.loader.Loader.doQuery(Loader.java:689) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2144) Awesome! The SQL query runs, but the Hibernate try to get the column by the original name, not by the alias, causing the error! It is not possible to correctly get the value of 2 different columns that have the same name!!!! Hint: why Hibernate use ResultSet.get* by column name instead of positional ResultSet.get* (1, 2, 3,...)? It will 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

14 years, 11 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2146) NullpointerException in DefaultDeleteEventListener.deleteTransientEntity

by Martin Kartumovich (JIRA)

NullpointerException in DefaultDeleteEventListener.deleteTransientEntity ------------------------------------------------------------------------ Key: HHH-2146 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2146 Project: Hibernate3 Type: Bug Versions: 3.2.0.cr5 Environment: Hibernate 3.2.0cr5, Oracle10g Reporter: Martin Kartumovich Priority: Blocker The following setup leads to a NPE in DefaultDeleteEventListener.deleteTransientEntity: Tables A, B Table V_A_B that is an M-N-Connection between A and B. Pojo for A has a Set of V_A_Bs. Pojo for B has a Set of V_A_Bs. Pojo C that has Sets of As and Bs. Cascades: all, delete-orphan -Create a new A and add a new V_A_B to its Set, that references to an existing B. -Delete B. -SaveOrUpdate Pojo C. In Hibernate 3.1.3 this works fine. In 3.2.0cr4+cr5 the removal of B results into an cascading removal of the never persisted V_A_B in the Set of B instead of ignoring it. This leads to an incorrect state where deleteTransientEntity is called with transientEnties=null. When now calling transientEnties.contains(...) the NPE is thrown. -- 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, 12 months

22
33
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2007