October 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3908) Expose way to fully control fetching in native-sql queries in API

by Steve Ebersole (JIRA)

Expose way to fully control fetching in native-sql queries in API ----------------------------------------------------------------- Key: HHH-3908 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3908 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Steve Ebersole Fix For: 3.5 Currently, in order to fully control fetching in native-sql queries, users must revert to using a named sql query (at least the xml, not sure if the annotations variety supports as well). We alreasy have all the objects/contracts in place to handle this for the named queries, just need to clean-up and properly document them. The current API calls to deal with this are the overloaded SQLQuery#addJoin methods. Ideally I'd see these changed to return the representation of the join-fetch to be configured; but addJoin already defines a return : the query itself :( So probably we will need new methods like addFetch: 1) public JoinFetch addFetch(String alias, String ownerAlias, String ownerProperty) 2) public JoinFetch addFetch(String alias, String ownerAlias, String ownerProperty, LockMode lockMode) interface JoinFetch { public void addPropertyMapping(String propertyName, String sqlAlias); } This can be expanded to the "root returns" as well (currently the overloaded #addEntity methods): public RootReturn addRoot(String alias, Class entityClass) etc... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Example ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SQLQuery query = session.createSQLQuery( "select c.cust_id as cid, " + " c.cust_name as cname, " + " o.order_id as oid, " + " o.order_num as onum " + " from customer c " + " inner join orders o " + " on c.cust_id = o.cust_id" ); query.addRoot( "c", Customer.class ) .addPropertyMapping( "id", "cid" ) .addPropertyMapping( "name", "cname" ); query.addFetch( "o", "c", "orders" ) .addPropertyMapping( "id", "oid" ) .addPropertyMapping( "orderNumber", "onum" ); ... -- 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, 5 months

2
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2350) 2nd level cache broken for inverse bidirectional one-to-many relation

by Burkhard Graves (JIRA)

2nd level cache broken for inverse bidirectional one-to-many relation --------------------------------------------------------------------- Key: HHH-2350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2350 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Database: MySQL, HSQL, ... (seems not to be important) Reporter: Burkhard Graves Attachments: testcase.tgz When using "inverse" one-to-many relations as described in "2.4.6.2.3. Bidirectional association with indexed collections" (http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.ht...) hibernate is wrong when activating 2nd level cache. See the attached example (unzip in /usr/local/hibernate-annotations-3.2.1.GA, testname=org.hibernate.test.annotations.invonetomany.InverseOneToManyTest). More details can be found here: http://forum.hibernate.org/viewtopic.php?t=969456 (and also in InverseOneToManyTest.java). -- 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, 5 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-3001) The NoopOptimizer needs to be synchronized

by Maciej Baranowski (JIRA)

The NoopOptimizer needs to be synchronized ------------------------------------------ Key: HHH-3001 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3001 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1, 3.2.6 Environment: 3.2.6, 3.2.4sp1, Oracle Reporter: Maciej Baranowski When SequenceStyleGenerator is used with Oracle it uses by default NoopOptimizer. The optimizer is not thread-safe and causes constraint violation errors while inserting data into the database. -- 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, 5 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3279) create series of maven plugins offering functionality of the ant tools

by Steve Ebersole (JIRA)

create series of maven plugins offering functionality of the ant tools ---------------------------------------------------------------------- Key: HHH-3279 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3279 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3.0.CR2 -- 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, 5 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3609) Invalid list re-ordering with IndexColumn and OneToMany association

by Martin Kovacik (JIRA)

Invalid list re-ordering with IndexColumn and OneToMany association ------------------------------------------------------------------- Key: HHH-3609 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3609 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1, Hibernate Tools 3.2.0, H2 database 1.0.69 Reporter: Martin Kovacik I want to map unidirectional OneToMany ordered list using annotations. My mapping is: public class Invoice { // ... @OneToMany(cascade = CascadeType.ALL) @JoinTable( name = "INVOICE_ITEM", joinColumns = {@JoinColumn(name = "invoice_id")}, inverseJoinColumns = {@JoinColumn(name = "item_id")} ) @Cascade(value = org.hibernate.annotations.CascadeType.DELETE_ORPHAN) @IndexColumn(name = "item_order") private List<Item> items = new ArrayList<Item>(); } The mapping of Item is not important here because I just want the association from Invoice to collection of Items to be unidirectional. The problem what hbm2ddl generates: create table INVOICE_ITEM ( invoice_id int8 not null, item_id int8 not null, item_order int4 not null, primary key (invoice_id, item_order), unique (item_id) ); alter table INVOICE_ITEM add constraint FK89837AD3EDA329D foreign key (item_id) references ITEM; alter table INVOICE_ITEM add constraint FK89837AD76A8E2D7 foreign key (invoice_id) references INVOICE; Another problem is how hibernate handles list re-ordering. If I want to change the item order (by manipulating invoice.items list) and then persist the changes hibernate tries to execute following sql: update INVOICE_ITEM set item_id=2 where invoice_id=1 and item_order=0 update INVOICE_ITEM set item_id=1 where invoice_id=1 and item_order=1 However this causes DB to complain about unique item_id constraint (which was generated by hibernate). IMHO hibernate should update just the item_order column. I think that this bug is related to ANN-679 (http://opensource.atlassian.com/projects/hibernate/browse/ANN-679). -- 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, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2269) Many-to-one cascade fails with TransientObjectException if the inverse collection is marked CascadeType.DELETE_ORPHAN

by Edward Costello (JIRA)

Many-to-one cascade fails with TransientObjectException if the inverse collection is marked CascadeType.DELETE_ORPHAN --------------------------------------------------------------------------------------------------------------------- Key: HHH-2269 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2269 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2, 3.2.1 Environment: Using hibernate annotations. Reporter: Edward Costello Attachments: TestBidirectionalCascade.java When both a many-to-one (child) and it's inverse one-to-many collection (on parent) are cascading. Attempting to save a child directly and cascade the save to the parent throws a TransientObjectException if the parent's collection is mapped CascadeType.DELETE_ORPHAN. For Example, with the classes below: @Entity public class Parent { @OneToMany(mappedBy = "parent") @Cascade(value = {CascadeType.ALL, CascadeType.DELETE_ORPHAN}) Set<DeleteOrphanChild> deleteOrphanChildren; } @Entity public class DeleteOrphanChild { @ManyToOne @Cascade(value = CascadeType.ALL) Parent parent; } Calling session.save() with an instance of the parent will cascade the save to the child as expected. However, calling save on an instance of the child will throw the TransientObjectException below while attempting to cascade the save to the parent. org.hibernate.TransientObjectException: cascade.test.TestBidirectionalCascade$DeleteOrphanChild at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:216) at org.hibernate.collection.AbstractPersistentCollection.getOrphans(AbstractPersistentCollection.java:889) at org.hibernate.collection.PersistentSet.getOrphans(PersistentSet.java:51) at org.hibernate.engine.CollectionEntry.getOrphans(CollectionEntry.java:350) at org.hibernate.engine.Cascade.deleteOrphans(Cascade.java:336) at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:318) at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:185) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:160) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:108) at org.hibernate.engine.Cascade.cascade(Cascade.java:248) at org.hibernate.event.def.AbstractSaveEventListener.cascadeAfterSave(AbstractSaveEventListener.java:437) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:326) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:108) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:98) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:509) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:501) at org.hibernate.engine.CascadingAction$1.cascade(CascadingAction.java:134) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:213) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:157) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:108) at org.hibernate.engine.Cascade.cascade(Cascade.java:248) at org.hibernate.event.def.AbstractSaveEventListener.cascadeBeforeSave(AbstractSaveEventListener.java:412) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:261) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:108) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186) at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175) at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:537) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:525) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:521) If the DELETE_ORPHAN cascade is removed the save works fine. The attached test case runs against an in memory HSQLDB database. It contains 4 tests, the second test (testSaveChildDeleteOrphan) fails showing the above exception. The other three pass showing that cascading from the parent works and that cascading in both directions remove if the DELETE_ORPHAN cascade is removed. We've only tested this with annotations, we haven't tried to reproduce it using hibernate mapping files. -- 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, 5 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3765) Fill the "end revision" column with appropriate data in add/mod/del/collection work units

by Adam Warski (JIRA)

Fill the "end revision" column with appropriate data in add/mod/del/collection work units ----------------------------------------------------------------------------------------- Key: HHH-3765 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3765 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski In case of modifications, not only the "end revision" column should be set on new data, but also modified on existing data. -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3764) Add the "end-revision" column when generating metadata

by Adam Warski (JIRA)

Add the "end-revision" column when generating metadata ------------------------------------------------------ Key: HHH-3764 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3764 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski The column would only be added if the necessary setting is set to true. The column will have the same type as the revision number, but will be nullable. -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3579) Support for PostgreSQL UUID data type

by Olivier Van Acker (JIRA)

Support for PostgreSQL UUID data type ------------------------------------- Key: HHH-3579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3579 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.3.1 Reporter: Olivier Van Acker PostgreSQL has since version 8.3 UUID as data type nativly supported in the database. The only way to get this to work in Hibernate is to add <column name="id" sql-type="uuid"/> to your mappings file (or @columnDefinition via annotations) and create your own custom usertype (e.g. public class UUIDUserType implements UserType, Serializable {..} ) and map this to java.util.UUID worth mentioning is that java.util.UUID is only introduced in java 1.5 so there might be a backwards compatibility 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, 6 months

5
22
0 / 0

[Hibernate-JIRA] Created: (HHH-2277) bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop

by Emmanuel Bernard (JIRA)

bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop -------------------------------------------------------------------------------- Key: HHH-2277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2277 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 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

14 years, 6 months

2
14
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2009