January 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4778) Need better handling of criteria expression casting

by Steve Ebersole (JIRA)

Need better handling of criteria expression casting --------------------------------------------------- Key: HHH-4778 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4778 Project: Hibernate Core Issue Type: Bug Components: entity-manager, query-criteria Affects Versions: 3.5.0-Beta-2 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Beta-3 CriteriaBuilder#toInteger, #toLong, et al. Currently we handle this as a simple in-memory conversion, which can, however, lead to overflows when the cast'ed expression is used in the select clause. The issue is the type Hibernate chooses to actually extract the values from the result set are not effected by the cast. -- 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

16 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4757) nextTimestamp not precise enough for Infinispan 2LC

by Galder Zamarreno (JIRA)

nextTimestamp not precise enough for Infinispan 2LC --------------------------------------------------- Key: HHH-4757 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4757 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-Beta-2 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 3.5 oing some tests we discovered that with Infinispan cached querys are not recognized as UpToDate when the query call (= the chache put) happens within 100ms after the last UpdateTimestamps invalidation. This is because Infinispan defines a rather low timestamp granular precision, indeed ehcache's precision goes into milliseconds. InfinispanRegionFactory.java: public long nextTimestamp() { return System.currentTimeMillis() / 100; } EHCache-TimeStamper: public static long next() { synchronized(Timestamper.class) { long newTime = System.currentTimeMillis() << BIN_DIGITS; if (time<newTime) { time = newTime; counter = 0; } else if (counter < ONE_MS - 1 ) { counter++; } return time + counter; } } regards G.D. -- 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

16 years, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4087) Session.flush() Causes AssertionFailure

by Brian (JIRA)

Session.flush() Causes AssertionFailure ---------------------------------------- Key: HHH-4087 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4087 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Reporter: Brian After calling Session.save() with an entity, calling Session.flush() causes the following error. org.hibernate.AssertionFailure: collection [com.example.myList] was not processed by flush() at org.hibernate.engine.CollectionEntry.postFlush(CollectionEntry.java:205) at org.hibernate.event.def.AbstractFlushingEventListener.postFlush(AbstractFlushingEventListener.java:333) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:28) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) The mapping used was: <component name="component" class="Component"> <property name="sequence" column="SEQUENCE" not-null="false" generated="insert"/> <list name="myList" table="MY_LIST"> <key column="MY_LIST_KEY"/> <index column="INDEX_COL"/> <composite-element class="MyCompositeElement"> <property name="element" column="ELEMENT"/> </composite-element> </list> </component> -- 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

16 years, 3 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4598) An embeddable class may contains collection of basic types or embeddable objects

by Emmanuel Bernard (JIRA)

An embeddable class may contains collection of basic types or embeddable objects -------------------------------------------------------------------------------- Key: HHH-4598 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4598 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

16 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4590) CASTs from CriteriaBuilder.toXXX methods still need to be fleshed out

by Steve Ebersole (JIRA)

CASTs from CriteriaBuilder.toXXX methods still need to be fleshed out --------------------------------------------------------------------- Key: HHH-4590 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4590 Project: Hibernate Core Issue Type: Bug Components: entity-manager, query-criteria, query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole The difficulty here is in terms of SELECT clause. If the casts are to be allowed in the SELECT clause then we need to dynamically account for the underlying org.hibernate.type.Type to use to read the results. Problematic because criteria is supposed to mirror the capabilities of the "query language", but there is no mention of any such functionality in the "query language" section. -- 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

16 years, 3 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-442) Upgrade existing code to Lucene 2.9.1

by Sanne Grinovero (JIRA)

Upgrade existing code to Lucene 2.9.1 ------------------------------------- Key: HSEARCH-442 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-442 Project: Hibernate Search Issue Type: Task Components: engine Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta2 This is not meant to add any new features, or make use of new features in Lucene 2.9: just to become compatible with Lucene 2.9 and be able to integrate later on new features and update to version 3.x.x -- 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

16 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4779) collection-cache and single-object-Cache (Ehcache) have different timestamps

by AnitaMuc (JIRA)

collection-cache and single-object-Cache (Ehcache) have different timestamps ---------------------------------------------------------------------------- Key: HHH-4779 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4779 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.3.2, 3.3.1 Environment: hibernate-core 3.3.1.GA / 3.3.2.GA hibernate-ehcache 3.3.1.GA / 3.3.2.GA Spring 2.5.6 Reporter: AnitaMuc The proxy-timestamps of a new saved object from the single-object-cache and from the collection-cache can differ about 1 ms. This causes a StaleObjectStateException when the object from the collection-cache gets merged (for example by cascade). This problem disappears when the 2LC (Ehcache) is deactivated. -- 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

16 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4701) ORA-00920: invalid relational operator using subquery

by Julien HENRY (JIRA)

ORA-00920: invalid relational operator using subquery ----------------------------------------------------- Key: HHH-4701 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4701 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2 Environment: Oracle 9i Reporter: Julien HENRY I have the following relations: A*---B*---C All my tables are using composite keys. I want to delete all A in relation to a specific C entity. My query is: delete from A a where a in (select a1 from A a1 left join a1.b b left join b.c c where c.compositeId=:cId) The resulting Oracle query is something like: delete from A where (A_1, A_2) in (select (A_1, A_2) from A a1, B b1, C c1 where [...]) which produce the following error: ORA-00920: invalid relational operator I tried to fix the SQL query by removing parenthesis: delete from A where (A_1, A_2) in (select A_1, A_2 from A a1, B b1, C c1 where [...]) which now give the following error: ORA-00918: column ambiguously defined And finally I arrived to a correct quesry by adding table prefix: delete from A where (A_1, A_2) in (select a1.A_1, a1.A_2 from A a1, B b1, C c1 where [...]) I will try to create a test case. Is there any documentation on how to provide test case? 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

16 years, 3 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3590) Having @version in Parent causes wrong HQL update when updating subclass in Joined Subclass Inheritance Strategy.

by Rachit (JIRA)

Having @version in Parent causes wrong HQL update when updating subclass in Joined Subclass Inheritance Strategy. ----------------------------------------------------------------------------------------------------------------- Key: HHH-3590 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3590 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.1 Environment: Java 1.5 , Oracle 10g , Hibernate 3.3.1.GA Reporter: Rachit Priority: Blocker A very simple joined subclass strategy implemented. 2 classes: Employee(parent/superclass) and Person( child/subclass) Employee has @Version defined on column ROW_VERSION and Person extends Employee using Joined Inheritance Strategy. Person has PERSON_ID as PK and Employee has EMPLOYEE_ID as PK. I also have @PrimaryKeyJoinColumn(name = "PERSON_ID", referencedColumnName = "EMPLOYEE_ID") for obvious reason. Now if I update any attribute in Child class i.e Person.setVIPFlag("Y") , hibernate fires an update query on Parent entity with wrong column name in hql. In this case the query would be "update EMPLOYEE set ROW_VERSION=? where PERSON_ID=? and ROW_VERSION=?". This query fails as EMPLOYEE does not have PERSON_ID. The moment I remove @Version annotation from Parent(Employee) class, there is no update ( as expected ) and hence no error, but this is not an acceptable solution. Thanking in anticipation. -- 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

16 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4777) org.hibernate.ejb.test.PackagedEntityManagerTest.testOverridenPar() hard code hsqldb connection info

by Strong Liu (JIRA)

org.hibernate.ejb.test.PackagedEntityManagerTest.testOverridenPar() hard code hsqldb connection info ---------------------------------------------------------------------------------------------------- Key: HHH-4777 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4777 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Beta-2, 3.3.2 Reporter: Strong Liu Fix For: 3.5.0-Beta-3 the method in the title hard code hsqldb connection info, and this does not be filterd when maven process resource, so this will fail on all DBs except hsqldb... and org.hibernate.ejb.test.pack.spacepar.Bug.comment, the "comment" is a keyword in oracle same as org.hibernate.ejb.test.pack.overridenpar.Bug.comment src/test/bundles/explicitpar/META-INF/orm.xml the id name "number" is a keyword in oracle -- 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

16 years, 3 months

1
3
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 January 2010