December 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5277) Build fails on some systems when using jdk 6

by Hardy Ferentschik (JIRA)

Build fails on some systems when using jdk 6 -------------------------------------------- Key: HHH-5277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5277 Project: Hibernate Core Issue Type: Bug Components: build Reporter: Hardy Ferentschik When building Core using Java 6 artifacts are renamed during install from *.jar to *.jdocbook-style (at list in the core sub-module). This of course screws up the local repo. Here is the build log of a _mvn install_ in the core module: {noformat} 517$ setJava 1.6 Configuring Shell Environment for Java 1.6 Current Java: java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-10M3065) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode) hardy@aleppo:~/work/hibernate/core/trunk/core 518$ mvn clean install -Dmaven.test.skip=true [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Hibernate Core [INFO] task-segment: [clean, install] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean {execution: default-clean}] [INFO] Deleting directory /Users/hardy/work/hibernate/core/trunk/core/target [INFO] [enforcer:enforce {execution: enforce-java}] [INFO] [antlr:generate {execution: default}] [INFO] Using Antlr grammar: /Users/hardy/work/hibernate/core/trunk/core/src/main/antlr/hql.g ANTLR Parser Generator Version 2.7.6 (2005-12-22) 1989-2005 warning: invalid command-line argument: -traceTreeParser; ignored [INFO] Using Antlr grammar: /Users/hardy/work/hibernate/core/trunk/core/src/main/antlr/hql-sql.g ANTLR Parser Generator Version 2.7.6 (2005-12-22) 1989-2005 warning: invalid command-line argument: -traceParser; ignored [INFO] Using Antlr grammar: /Users/hardy/work/hibernate/core/trunk/core/src/main/antlr/sql-gen.g ANTLR Parser Generator Version 2.7.6 (2005-12-22) 1989-2005 warning: invalid command-line argument: -traceParser; ignored [INFO] Using Antlr grammar: /Users/hardy/work/hibernate/core/trunk/core/src/main/antlr/order-by.g ANTLR Parser Generator Version 2.7.6 (2005-12-22) 1989-2005 warning: invalid command-line argument: -traceTreeParser; ignored [INFO] Using Antlr grammar: /Users/hardy/work/hibernate/core/trunk/core/src/main/antlr/order-by-render.g ANTLR Parser Generator Version 2.7.6 (2005-12-22) 1989-2005 warning: invalid command-line argument: -traceParser; ignored [INFO] [resources:resources {execution: default-resources}] [WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 3 resources [INFO] Copying 5 resources [INFO] [compiler:compile {execution: default-compile}] [INFO] Compiling 1306 source files to /Users/hardy/work/hibernate/core/trunk/core/target/classes [INFO] [injection:bytecode {execution: default}] [INFO] writing injection changes back [/Users/hardy/work/hibernate/core/trunk/core/target/classes/org/hibernate/Version.class] [INFO] [resources:testResources {execution: default-testResources}] [WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 1 resource [INFO] [compiler:testCompile {execution: default-testCompile}] [INFO] Not compiling test sources [INFO] [surefire:test {execution: default-test}] [INFO] Tests are skipped. [INFO] [jar:jar {execution: default-jar}] [INFO] Building jar: /Users/hardy/work/hibernate/core/trunk/core/target/hibernate-core-3.6.0-SNAPSHOT.jar [INFO] [source:jar-no-fork {execution: attach-sources}] [INFO] Building jar: /Users/hardy/work/hibernate/core/trunk/core/target/hibernate-core-3.6.0-SNAPSHOT-sources.jar [INFO] [install:install {execution: default-install}] [INFO] Installing /Users/hardy/work/hibernate/core/trunk/core/target/hibernate-core-3.6.0-SNAPSHOT.jar to /Users/hardy/tmp/m2/org/hibernate/hibernate-core/3.6.0-SNAPSHOT/hibernate-core-3.6.0-SNAPSHOT.jdocbook-style [INFO] Installing /Users/hardy/work/hibernate/core/trunk/core/target/hibernate-core-3.6.0-SNAPSHOT-sources.jar to /Users/hardy/tmp/m2/org/hibernate/hibernate-core/3.6.0-SNAPSHOT/hibernate-core-3.6.0-SNAPSHOT-sources.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1 minute 15 seconds [INFO] Finished at: Fri May 28 15:29:33 CEST 2010 [INFO] Final Memory: 43M/211M [INFO] ------------------------------------------------------------------------ {noformat} The maven version is: _Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)_ Strong was able to reproduce the problem on his Fedora box, but on this Mac it works. -- 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

5
13
0 / 0

[Hibernate-JIRA] Créée: (HHH-2389) Improving DB2 dialect

by Nicolas Billard (JIRA)

Improving DB2 dialect --------------------- Key: HHH-2389 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2389 Project: Hibernate3 Type: Improvement Components: query-hql Versions: 3.2.1 Environment: Development based on v 3.2.1 Reporter: Nicolas Billard Priority: Minor Attachments: DB2Dialect.java The class joined to this issue overrides the DB2 dialect. The dialect included in hibernate doesn't work very well when you want to limit returned results (when you call setFirstResult and / or setMaxResults on a query) : - the instructions "fetch first XXX row only is not used - a temporary table is used when it's not usefull - when you have subselects, an exception can occur if subselects have order by clause (because of the getRowNumber method, not corrected here). This version of getLimitString() method generates faster requests (tests made on a table of 300000 rows shows that fetching rows from 20 to 30 takes 0.3 seconds with original version, 0.02 with this one). -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5434) org.hibernate.test.filter.DynamicFilterTest testSqlSyntaxOfFiltersWithUnions fails with Ingres dialect

by Ray Fan (JIRA)

org.hibernate.test.filter.DynamicFilterTest testSqlSyntaxOfFiltersWithUnions fails with Ingres dialect ------------------------------------------------------------------------------------------------------ Key: HHH-5434 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5434 Project: Hibernate Core Issue Type: Patch Components: core, testsuite Affects Versions: 3.6.0.Beta1 Environment: Hibernate core 3.6.0-SNAPSHOT, Ingres 10.0.0 (int.lnx/128) Reporter: Ray Fan org.hibernate.test.filter.DynamicFilterTest testSqlSyntaxOfFiltersWithUnions fails with Ingres dialect because the use of unions within a where clause are not supported. -- 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
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5572) clean up Sybase job failures

by Strong Liu (JIRA)

clean up Sybase job failures ---------------------------- Key: HHH-5572 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5572 Project: Hibernate Core Issue Type: Bug Components: annotations, core Environment: sybase ase 15.0/5 Reporter: Strong Liu Assignee: Strong Liu most of failures are caused by the keywords and nullable column in pk constraints -- 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: (HHH-5007) Using <formula> within Composite Element inside Collection

by Hepoi Ko (JIRA)

Using <formula> within Composite Element inside Collection ---------------------------------------------------------- Key: HHH-5007 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5007 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5.0-CR-2 Environment: 3.5.0-CR2, AS400, Component Reporter: Hepoi Ko Priority: Minor Attachments: JoinWalker.java I was one of the user who use Hibernate in a legacy database schema, and always had a issue on using composite-key (and formula) inside collection. I was able to modify the hibernate source (from 3.3.2) to overcome such issue. I am hoping the new version 3.5.0 would even fix this problem. Anyway, I just leave the fix information here, hope it would help. In /org/hibernate/loader/JoinWalker.java Line 641: String[] aliasedLhsColumns = StringHelper.qualify(alias, lhsColumns); Modify with these: String[] fullAliasedLhsColumns = persister.getElementColumnNames(alias); String[] aliasedLhsColumns = ArrayHelper.slice(fullAliasedLhsColumns, begin, length); Without above change I would get NullPointerException on a mapping as .... <set name="auditRecords" table="OEP40A" order-by="ADAT40 DESC, ATIM40 DESC" mutable="false" inverse="true" outer-join="true"> <key> <column name="CONO40"></column> <column name="ORDN40"></column> </key> <composite-element class="com.ricoh.erp.order.domain.OrderAudit"> <property name="userId"> <column name="AUSR40"></column> </property> <property name="workstationId"> <column name="AWRK40"></column> </property> <many-to-one name="customerEntry" not-found="ignore"> <formula>CONO40</formula>  <column name="CUSN40"></column> <column name="DSEQ40"></column> </many-to-one> </composite-element> With Best Regards, -- 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
15
0 / 0

[Hibernate-JIRA] Created: (HHH-5735) Usage Path.type() in expressions throws java.lang.IllegalArgumentException

by Jaroslaw Lewandowski (JIRA)

Usage Path.type() in expressions throws java.lang.IllegalArgumentException --------------------------------------------------------------------------- Key: HHH-5735 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5735 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.6.0, 3.6.1 Reporter: Jaroslaw Lewandowski Priority: Blocker Attachments: InheritanceTest.tgz It is not possible to filter entities using Path.type() in Criteria Query API. Using type() in expressions throws an exception: Unexpected call on EntityTypeExpression#render java.lang.IllegalArgumentException: Unexpected call on EntityTypeExpression#render at org.hibernate.ejb.criteria.expression.PathTypeExpression.render( at org.hibernate.ejb.criteria.expression.PathTypeExpression.render(PathTypeExpression.java:48PathTypeExpression.java:48) ) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at foo.InheritanceTest.critQryTest(InheritanceTest.java:55) Test case is attached and it's similar to an example from JPA 2.0 specification - chapter 6.5.7 Example 2: CriteriaQuery<Employee> q = cb.createQuery(Employee.class); Root<Employee> emp = q.from(Employee.class); q.select(emp) .where(cb.notEqual(emp.type(), Exempt.class)); -- 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

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5742) PersistentSet#iterator() iterates over element which had been removed from set

by Guenther Demetz (JIRA)

PersistentSet#iterator() iterates over element which had been removed from set ------------------------------------------------------------------------------ Key: HHH-5742 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5742 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0, 3.5.0-Final Environment: 3.6.0FINAL, database indipendent (attached testcase based on hsqldb) Reporter: Guenther Demetz Priority: Critical Attachments: TestIterateOverExtraLazyCollectionWithInverseOwner.jar PRECONDITONS: -the relation is declared OneToMany with inverse owner (=mappedBy attribute specified) -the relation is declared extra lazy @LazyCollection (LazyCollectionOption.EXTRA) BUG: PersistenSet.iterator().next() returns element which previously had been removed from the set myPersistenSet.remove(obj); assertFalse(myPersistenSet.iterator().next() == obj); CAUSE: PersistentSet#iterator() implementation does differ from PersistentSet#contains() and PersistentSet#size() as it doesn't call the necessary flush() if: - the set isn't initialized - the set is declared extra lazy - the set has queued Operations (hasQueuedOperations == true) to be flushed Please see attached TESTCASE for more details. This IMHO is a critical bug, as it could create serious damage to companies using hibernate: imagine a company cancels a order-position and nevertheless the canceled position is subsequently delivered or/and invoiced to the customer, because the iterator returns the removed element. Thanks for attention. -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5313) Enabled filters, cache mode, and flush mode are not propagated to a new session via NonFlushedChanges

by Gail Badner (JIRA)

Enabled filters, cache mode, and flush mode are not propagated to a new session via NonFlushedChanges ----------------------------------------------------------------------------------------------------- Key: HHH-5313 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5313 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x, 3.6 Enabled filters, cache mode, and flush mode are not propagated to a new session via NonFlushedChanges. -- 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
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5811) flush causes update query on field of type Byte[]

by K C (JIRA)

flush causes update query on field of type Byte[] ------------------------------------------------- Key: HHH-5811 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5811 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.0 Environment: Hibernate 3.6.0.Final, Oracle 11g Reporter: K C I have a field that is mapped as follows: @Lob @Column(name = "picture") private Byte[] picture; When retrieving the entity with a regular session.load() or criteria.list(), upon session flush, an update statement is issued for the field. In an interceptor, I can see in the onFlushDirty method that the byte arrays in the currentState en previousState parameters are different objects, but with the same byte-content. All the other objects in currentState and previousState are identical. My guess is that this causes Hibernate to think the contents of the field changed? This behavior did not happen in 3.5.5-Final, and because the entity is versioned, upon each retrieval, the version field is incremented, which is highly undesirable. -- 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
13
0 / 0

[Hibernate-JIRA] Created: (HHH-5574) HQL ORDER BY descending component is not generated properly; DESC is only applied to the last component column

by Gail Badner (JIRA)

HQL ORDER BY descending component is not generated properly; DESC is only applied to the last component column --------------------------------------------------------------------------------------------------------------- Key: HHH-5574 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5574 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.6.0.CR1, 3.5.6 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.6.x HQL ORDER BY descending component is not generated properly; DESC is only applied to the last component column. For example: HQL: select z.name, z.address from org.hibernate.test.hql.Zoo z order by z.address DESC, z.name DESC SQL: select zoo0_.name as col_0_0_, zoo0_.street as col_1_0_, zoo0_.city as col_1_1_, zoo0_.postalCode as col_1_2_, zoo0_.country as col_1_3_, zoo0_.state_prov_id as col_1_4_ from Zoo zoo0_ order by zoo0_.street, zoo0_.city, zoo0_.postalCode, zoo0_.country, zoo0_.state_prov_id DESC, zoo0_.name DESC -- 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
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2010