February 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2975) Interceptor onFlushDirty collections - previous and current state the same instance

by Clayton J. Kovar (JIRA)

Interceptor onFlushDirty collections - previous and current state the same instance ----------------------------------------------------------------------------------- Key: HHH-2975 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2975 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Hibernate 3.2.2 - Oracle thin driver 10.1.0.4.0 Reporter: Clayton J. Kovar When calling Session.merge(entity) {therefore the previous state is available} the interceptor's onFlushDirty is called and the previous state for all of the simple properties correctly passes the previous values but with a collection the same collection instance is passed in both the previous and current state arrays. So far I have only seen this behavior on a Map with a one-to-many relationship to another entity. I have not tried it yet with Lists, Sets, or Bags. I'm assuming this is not expected behavior, but please let me know if it is. 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

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4895) query against derived id doesn't return expected result

by Scott Marlow (JIRA)

query against derived id doesn't return expected result ------------------------------------------------------- Key: HHH-4895 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4895 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Beta-4 Reporter: Scott Marlow Fix For: 3.5.0-Next query against derived id value doesn't return entity. -- 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, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4890) Nested @generatedValue generators don't seem to get their DDL generated.

by Emmanuel Bernard (JIRA)

Nested @generatedValue generators don't seem to get their DDL generated. ------------------------------------------------------------------------ Key: HHH-4890 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4890 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.0-Beta-4 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, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4894) Process composite-id sub-generators PersistentIdentifierGenerator contract(s)

by Steve Ebersole (JIRA)

Process composite-id sub-generators PersistentIdentifierGenerator contract(s) ----------------------------------------------------------------------------- Key: HHH-4894 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4894 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.0-Beta-4 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Next -- 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, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.

by Paul Andrews (JIRA)

Collection is not associated with any session exception when doing an eager fetch on a non-unique collection. ------------------------------------------------------------------------------------------------------------- Key: HHH-2862 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862 Project: Hibernate3 Issue Type: Bug Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5 Reporter: Paul Andrews It is basically caused by having an eager collection where the key of the collection is not unique in the results. The code works as follows in CollectionType.getCollection(): .... persistenceContext.addUninitializedCollection( persister, collection, key ); // some collections are not lazy: if ( initializeImmediately( entityMode ) ) { session.initializeCollection( collection, false ); } else if ( !persister.isLazy() ) { persistenceContext.addNonLazyCollection( collection ); } if ( hasHolder( entityMode ) ) { session.getPersistenceContext().addCollectionHolder( collection ); } if persistenceContext.addUninitializedCollection() detects that the collection with the given key has already been added it clears the session on the old instance of the collection (sets it to null). However, that collection has already been added to the persistence context by an earlier call to this method. So later when StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through all of the collections in the persistence context (including those which have had their session set to null by addUninitializedCollection()), calling forceInitialization() which throws a 'collection is not associated with any session' exception. -- 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, 2 months

10
11
0 / 0

[Hibernate-JIRA] Created: (HHH-4893) Multiple Joins using criteria

by praveer gupta (JIRA)

Multiple Joins using criteria ----------------------------- Key: HHH-4893 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4893 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.3.2 Reporter: praveer gupta I need to do multiple joins between two tables using Hibernate criteria. I tried doing the following: Crtieria criteria = session.createCriteria(Cat.class, "cat"); criteria.createAlias("cat.kittens", "first", CriteriaSpecification.LEFT_JOIN) .add( Restrictions.eq("first.name", "Foo")); criteria.createAlias("cat.kittens", "second", CriteriaSpecification.LEFT_JOIN) .add( Restrictions.eq("second.name", "Bar")); criteria.list(); I get the following: org.hibernate.QueryException: duplicate association path I tried looking for issues regarding the same and found http://opensource.atlassian.com/projects/hibernate/browse/HB-555. I am not aware whether we can do multiple joins using criteria now. -- 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, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4892) Simplify testing of persistence packages

by Steve Ebersole (JIRA)

Simplify testing of persistence packages ---------------------------------------- Key: HHH-4892 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4892 Project: Hibernate Core Issue Type: Task Components: entity-manager, testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Next This affects a number of tests and makes them impossible to run in IDE without setup. -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1803) Allow fetching with criteria when scrolling

by Corey Puffalt (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1803?page=c... ] Corey Puffalt commented on HHH-1803: ------------------------------------ I'd also like to know why this issue is being ignored when a patch is available. Also, I'm not so sure this should be listed as an enhancement when the API already allows one to do a scroll() and no exception or anything is thrown when scrolling over a Criteria with one-to-many relationship(s) and FetchMode.JOIN specified. Instead, we get a silent corruption of the results! > Allow fetching with criteria when scrolling > ------------------------------------------- > > Key: HHH-1803 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1803 > Project: Hibernate Core > Issue Type: Improvement > Components: query-criteria > Affects Versions: 3.2.0.cr2 > Reporter: Maarten Winkels > Attachments: Child.java, criteria-scroll-fetch-collection.patch, CriteriaScrollFetchTest.java, Diffs-applied-to-3.3.2.GA.zip, Parent.java, ParentChild.hbm.xml > > > When querying by criteria, fetching is allowed, but when scrolling a criteria, the fetching corrupts the result. -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1283) ScrollableResults JoinFetch don't set child collection correctly　after the second parent object

by Corey Puffalt (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1283?page=c... ] Corey Puffalt commented on HHH-1283: ------------------------------------ What does it take to get this issue fixed? As noted by others there's a proposed patch submitted on one of the other duplicate tickets but still no one cares? > ScrollableResults JoinFetch don't set child collection correctly　after the second parent object > ----------------------------------------------------------------------------------------------- > > Key: HHH-1283 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1283 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 > Environment: Hibernate 3.1 > Oracle10gR2 > Oracle JDBC Driver 10.2.0.1.0 > Sun JDK 1.5.0_06 > Spring 1.2.6 > Reporter: Masahiro Hirashima > Attachments: ScrollableCollectionFetchingTest.java, ScrollableResults.zip > > > ScrollableResults JoinFetch set child collection correctly at first parent object. > but after the second parent object, It set only the first element of a child collection. > I made the following tables. > CREATE TABLE owners ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > first_name VARCHAR(30), > last_name VARCHAR(30), > address VARCHAR(255), > city VARCHAR(80), > telephone VARCHAR(20), > version NUMBER(36, 0) DEFAULT 0 > ); > CREATE TABLE types ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > name VARCHAR(80), > version NUMBER(36, 0) DEFAULT 0 > ); > CREATE TABLE pets ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > name VARCHAR(30), > birth_date DATE, > type_id NUMBER(36, 0), > owner_id NUMBER(36, 0), > version NUMBER(36, 0) DEFAULT 0 > ); > and inserted the following data. > INSERT INTO owners VALUES (1, 'Betty', 'Davis', '638 Cardinal Ave.', 'Sun Prairie', '6085551749', 0); > INSERT INTO owners VALUES (2, 'Eduardo', 'Rodriquez', '2693 Commerce St.', 'McFarland', '6085558763', 0); > INSERT INTO pets VALUES (1, 'Leo', '2000-09-07', 1, 1, 0); > INSERT INTO pets VALUES (2, 'Basil', '2002-08-06', 2, 1, 0); > INSERT INTO pets VALUES (3, 'Rosy', '2001-04-17', 3, 2, 0); > INSERT INTO pets VALUES (4, 'Jewel', '2000-03-07', 4, 2, 0); > INSERT INTO pets VALUES (5, 'Iggy', '2000-11-30', 5, 2, 0); > INSERT INTO types VALUES (1, 'cat', 0); > INSERT INTO types VALUES (2, 'dog', 0); > INSERT INTO types VALUES (3, 'lizard', 0); > INSERT INTO types VALUES (4, 'snake', 0); > INSERT INTO types VALUES (5, 'bird', 0); > and I execute following code. > String hqlJoinFetchTest = > "from Owner owner " + > "left outer join fetch owner.pets as pets " + > "left outer join fetch pets.type " + > "order by owner.firstName, owner.lastName"; > Query query = session.createQuery(hqlJoinFetchTest); > ScrollableResults cursor = query.scroll(); > while ( cursor.next() ) { > Owner owner = (Owner)cursor.get(0); > System.out.println(owner); > } > result of this code is following. > petclinic.domain.Owner@15d616e[id=1,version=0,firstName=Betty,lastName=Davis, > petclinic.domain.Pet@136d9d8[id=2,version=0,name=Basil,birthDate=2002-08-06, > petclinic.domain.PetType@1be2893[id=2,version=0,name=dog] > petclinic.domain.Pet@14a75bb[id=1,version=0,name=Leo,birthDate=2000-09-07, > petclinic.domain.PetType@17779e3[id=1,version=0,name=cat] > petclinic.domain.Owner@e3570c[id=2,version=0,firstName=Eduardo,lastName=Rodriquez > petclinic.domain.Pet@167e3a5[id=4,version=0,name=Jewel,birthDate=2000-03-07, > petclinic.domain.PetType@1926e90[id=4,version=0,name=snake] > First owner object set collection collectly. > but second owner object don't set second pet object(id=5) and third pet object(id=6). -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4704) Pass session into EntityTuplizer#setIdentifier

by Steve Ebersole (JIRA)

Pass session into EntityTuplizer#setIdentifier ---------------------------------------------- Key: HHH-4704 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4704 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Next This is needed for the incredibly intelligent JPA derived-identity "feature" Will also require passing session into EntityPersister#setIdentifier -- 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, 2 months

1
4
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 February 2010