November 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5311) + operator in JPQL subselect query results in NullPointerException

by Grzegorz Olędzki (JIRA)

+ operator in JPQL subselect query results in NullPointerException ------------------------------------------------------------------ Key: HHH-5311 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5311 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Environment: hibernate-3.5.0-Final.jar, java version "1.6.0_17", database platform seems irrelevant (H2 and MySQL tested) Reporter: Grzegorz Olędzki When trying to use a {{+}} arithmetic operator in a subquery of my JPQL query I end up with a NullPointerException from {{org.hibernate.hql.ast.HqlSqlWalker}}. I've played with adding/removing parentheses, aliases, but that doesn't seem to help. -- 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, 5 months

2
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5657) Assembly needs to exclude .git

by Steve Ebersole (JIRA)

Assembly needs to exclude .git ------------------------------ Key: HHH-5657 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5657 Project: Hibernate Core Issue Type: Bug Components: build Affects Versions: 3.6.0 Reporter: Steve Ebersole Fix For: 3.6.1 While the Maven assembly plugin automatically excludes other types of SCM meta files/directoies, that is apprently not the case for Git. So we will need to manually exclude .git when building the assemblies. -- 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, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3551) Boolean substitution in informix

by Rouvignac (JIRA)

Boolean substitution in informix -------------------------------- Key: HHH-3551 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3551 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.3.1 Environment: Hibernate 3.2 Informix 9.40 Reporter: Rouvignac HQL Query : select order from Order order where order.printed = ? Parameter : true, false, Boolean.TRUE or Boolean.FALSE When the request is executed we get the following error : SQLSTATE: IX000 SQL CODE: -674 674: Routine (equal) can not be resolved. If as parameter we use "t" ot "f" everything works fine but it will not work with other DB. As a workaround we can use : property name="hibernate.query.substitutions">true t, false f</property> I investigated in Dialects : Dialect.java public String toBooleanValueString(boolean bool) { return bool ? "1" : "0"; } PostgreSQLDialect.java public String toBooleanValueString(boolean bool) { return bool ? "true" : "false"; } InformixDialect.java uses Dialect.java toBooleanValueString method. In my mind toBooleanValueString should be added to InformixDialect.java as follow : public String toBooleanValueString(boolean bool) { return bool ? "t" : "f"; } -- 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, 5 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3984) onPrepareStatement is called twice.

by Tobias Bergman (JIRA)

onPrepareStatement is called twice. ----------------------------------- Key: HHH-3984 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3984 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5 Environment: Windows, MySQL 5, Java 1.6 Reporter: Tobias Bergman onPrepareStatement is called twice when batched. First getSQL(sql) (which will call the interceptor) is called from prepareBatchStatement. After the invokation the prepareBatchStatement() will call prepareStatement(sql) which will also call getSQL(). -- 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, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4511) Problems with polymorphic queries with SINGLE_TABLE inheritance strategy

by Karoly Gacsal (JIRA)

Problems with polymorphic queries with SINGLE_TABLE inheritance strategy ------------------------------------------------------------------------ Key: HHH-4511 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4511 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0.Beta-1 Environment: envers 1.2.1 Hibernate 3.3.2 Reporter: Karoly Gacsal Attachments: ChildAuditing.java Inheritance strategy is SINGLE_TABLE (discriminator). When I query for ParentType I do not get ChildType instances in the result, but ParentType instances. I checked the problem against envers 1.2.1/Hibernate 3.3.2 and against Hibernate 3.5.0.Beta-1 too. The testcase "\src\test\java\org\hibernate\envers\test\integration\inheritance\single\ChildAuditing.java" passes, but when I change the two sides of the equals method in testPolymorphicQuery()'s second assert the testcase fails, because the expected result is a ChildEntity, but in the result we get an instance of ParentEntity. Attached you can find the testcases changed by me. -- 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, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5095) BasicLoader.isBag() checks type assignability wrongly

by Matt Benson (JIRA)

BasicLoader.isBag() checks type assignability wrongly ----------------------------------------------------- Key: HHH-5095 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5095 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Environment: N/A Reporter: Matt Benson Method defined as: {code} private boolean isBag(CollectionPersister collectionPersister) { return collectionPersister.getCollectionType().getClass().isAssignableFrom( BagType.class ); } {code} Will never return true if the returned CollectionType subclasses BagType; should IMO be: {code} private boolean isBag(CollectionPersister collectionPersister) { return BagType.class.isInstance( collectionPersister.getCollectionType() ); } {code} My humble apologies for the submission without a test case, but this one feels pretty simple. Thanks! -- 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, 5 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5236) Exception with hibernate model

by Michael Zhang (JIRA)

Exception with hibernate model ------------------------------ Key: HHH-5236 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5236 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2, 3.5.0-Final, 3.2.0.ga Environment: Java 1.5 Windows/Unix Reporter: Michael Zhang I have a hibernate model class member e.g. (active) that is mapped to a string (either "Y" or "N"). Both getter and setter are implemented. There is also another method in the class: public boolean isActive()... When test it from JUnit, everything works fine. However when the class is accessed from thread with database update operation, hibernate will throw ClassCast exception from Boolean to String. If the method of "isActive" is changed to something else such as "isActiveMethod", the exception will disappeare. -- 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, 5 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5548) org.hibernate.test.naturalid.immutable.ImmutableNaturalIdTest hangs on completion with Ingres10Dialect

by Ray Fan (JIRA)

org.hibernate.test.naturalid.immutable.ImmutableNaturalIdTest hangs on completion with Ingres10Dialect ------------------------------------------------------------------------------------------------------ Key: HHH-5548 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5548 Project: Hibernate Core Issue Type: Bug Components: core, testsuite Affects Versions: 3.6.0.Beta4 Environment: hibernate-core-3.6.0.Beta4, Ingres II 10.0.0 (int.lnx/131) NPTL Reporter: Ray Fan Priority: Minor Attachments: ImmutableNaturalIdTest.java.svn.diff When running the ImmutableNaturalIdTest suite the test hangs on a "drop table IMM_NAT_ID_USER" at the end of the test. This is determined to be caused by an orphaned session that has completed a select query and not releasing the physical database resources. -- 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, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5621) NPE (in ReflectHelper.getConstructor) during createQuery without alias with one entity (wich use several tables)

by Félix Gerzaguet (JIRA)

NPE (in ReflectHelper.getConstructor) during createQuery without alias with one entity (wich use several tables) ---------------------------------------------------------------------------------------------------------------- Key: HHH-5621 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5621 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.CR2 Environment: Gentoo Linux Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Hibernate 3.6.0.CR2 tested DB: PostgreSQL 8.4, HSQLDB 1.8.0.10 Reporter: Félix Gerzaguet Priority: Minor Attachments: TestCaseCreateQueryWithoutAliasNPE.jar During a session.createQuery like: Query query6 = session.createQuery("select new Something(id, event, dummyField) " + "from Something" ); A NPE is thrown: Exception in thread "main" java.lang.NullPointerException at org.hibernate.util.ReflectHelper.getConstructor(ReflectHelper.java:343) at org.hibernate.hql.ast.tree.ConstructorNode.resolveConstructor(ConstructorNode.java:176) at org.hibernate.hql.ast.tree.ConstructorNode.prepare(ConstructorNode.java:150) at org.hibernate.hql.ast.HqlSqlWalker.processConstructor(HqlSqlWalker.java:996) I join an test case. All versions of hibernate seems affected (from 3.2.6.ga to 3.6.0.RC2). This is a minor issue since an easy workaround is available: you just have to use an alias to qualifie the properties For the preceding example, we will have: Query query3 = session.createQuery("select new Something(sthg.id, sthg.event, sthg.dummyField) " + "from Something sthg" ); Possible fix: As described in the testCase, I fix this by a one character fix: In org.hibernate.hql.ast.HqlSqlWalker in method isNonQualifiedPropertyRef, change from if ( fromElements.size() == 1 ) { to if ( fromElements.size() >= 1 ) { This could means that when a property is not qualified, we leave a chance for this property to be found on the first explicit element of the from clause. I test this fix on the 3.5.5-Final code and I was able to run the test suite without failures. I can't think of a test case in which this fix could lead to a regression but I'm not an Hibernate Guru so comments are welcome. -- 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, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5666) Missing table alias for one column in generated sql

by Jakub Jankowski (JIRA)

Missing table alias for one column in generated sql --------------------------------------------------- Key: HHH-5666 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5666 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2, MySQL Reporter: Jakub Jankowski Column 'desc' in generated sql doesn't have table alias 'announceme0_' (unlike the rest of columns) which genereates error while executing. Genereted sql: select announceme0_.announcementID as announce1_1_0_, announceme0_.oceaneqID as oceaneqID1_0_, announceme0_.fileName as fileName1_0_, desc as desc1_0_ from test.announcement announceme0_ where announceme0_.announcementID=1 Mapping for the table: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">  <hibernate-mapping> <class name="all.model.Announcement" table="announcement" catalog="test"> <id name="announcementId" type="int"> <column name="announcementID" /> <generator class="assigned" /> </id> <property name="oceaneqId" type="java.lang.Integer"> <column name="oceaneqID" /> </property> <property name="fileName" type="string"> <column name="fileName" length="1024" /> </property> <property name="desc" type="string"> <column name="desc" length="1024" /> </property> <set name="routeOnAnnouncements" inverse="true"> <key> <column name="announcementID" /> </key> <one-to-many class="all.model.RouteOnAnnouncement" /> </set> </class> </hibernate-mapping> There's no such problem with other tables. -- 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, 5 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2010