February 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3146) PojoInstantiator has no nice extension points.

by Ali Ibrahim (JIRA)

PojoInstantiator has no nice extension points. ---------------------------------------------- Key: HHH-3146 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3146 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Ali Ibrahim Priority: Minor PojoInstantiator is very difficult to extend meaningfully because all of its state is private. It would nice to have an easy way to extend it to perform different behavior such as proxying all entities. The fix would either to be expose more internal state or to create some judicious overrideable methods that allow extension. -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3145) HbmBinder is used with static methods

by Ali Ibrahim (JIRA)

HbmBinder is used with static methods ------------------------------------- Key: HHH-3145 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3145 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Ali Ibrahim Priority: Minor HbmBinder is used in a static manner. This makes it impossible to changed how the configuration file is read without copying all the classes that call HbmBinder. Fix is to make all the static methods on HbmBinder instance methods and change external references to call instance methods on shared HbmBinder. Static methods are usually evil anyway :). -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3143) The initializeCollectionFromCache method in DefaultInitializeCollectionListener is private

by Ali Ibrahim (JIRA)

The initializeCollectionFromCache method in DefaultInitializeCollectionListener is private ------------------------------------------------------------------------------------------ Key: HHH-3143 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3143 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Ali Ibrahim The initializeCollectionFromCache method in DefaultInitializeCollectionListener is private. If you would like to extend this class and only change the load from the data source logic then you have to copy this method. Fix is to change this method's visibility to protected. -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3142) JndiBoundTreeCacheProvider

by Arun Kumarr (JIRA)

JndiBoundTreeCacheProvider -------------------------- Key: HHH-3142 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3142 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.3 Environment: My SQL, Hibernate 3.2.3 Reporter: Arun Kumarr Please refer the page, http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132986#4132986 The TreeCacheMbean obtained from JRMP proxy is typecasted to TreeCache. -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3139) select elements(collection) does not return all composite key segments when used in subquery

by Carl Allain (JIRA)

select elements(collection) does not return all composite key segments when used in subquery -------------------------------------------------------------------------------------------- Key: HHH-3139 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3139 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4 Environment: HB 3, Oracle 10g Reporter: Carl Allain Priority: Blocker When dealing with collection of entities having composite keys, elements() seems to return all key segment columns, which seems fine. So, in our case (CountrySubdivision has a composite PK, :CTRSD_CD + CTR_ISO_CD), when we do select elements(mks.countrySubdivisions) from MarketSegmentPdo mks it gives this: select countrysub1_.CTRSD_CD as col_0_0_, countrysub1_.CTR_ISO_CD as col_0_1_ from MKSG_MKS marketsegm0_, MKSG_MKSCTRSD countrysub1_ where marketsegm0_.MKS_NRI=countrysub1_.MKS_NRI while using the same elements() function construct in a subquery, only one PK segment is included by Hibernate!. So: from CountrySubdivisionPdo cs where cs.id in (select elements(mks.countrySubdivisions) from MarketSegmentPdo mks) gives this: select countrysub0_.CTRSD_CD as CTRSD1_65_, countrysub0_.CTR_ISO_CD as CTR2_65_, countrysub0_.CTRSD_TS as CTRSD3_65_ from PLGE_CTRSD countrysub0_ where ( countrysub0_.CTRSD_CD, countrysub0_.CTR_ISO_CD ) in ( select countrysub2_.CTRSD_CD <---------------------------------- WHERE is CTR_ISO_CD??????? from MKSG_MKS marketsegm1_, MKSG_MKSCTRSD countrysub2_ where marketsegm1_.MKS_NRI=countrysub2_.MKS_NRI ) -- 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

18 years, 1 month

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3138) make constructor of DynamicMapEntityTuplizer public

by Lars Fischer (JIRA)

make constructor of DynamicMapEntityTuplizer public --------------------------------------------------- Key: HHH-3138 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3138 Project: Hibernate3 Issue Type: Task Components: core Affects Versions: 3.2.6 Reporter: Lars Fischer Priority: Minor The constructor of DynamicMapEntityTuplizer should be public to enable the creation of DynamicMapEntityTuplizer subclasses. -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3134) documentation module in a profile

by Aleksandar Kostadinov (JIRA)

documentation module in a profile --------------------------------- Key: HHH-3134 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3134 Project: Hibernate3 Issue Type: Sub-task Components: core, documentation Affects Versions: 3.3 Reporter: Aleksandar Kostadinov Can we have the documentation module of the core project in a profile so it can be disabled if needed? It still has issues building as well depends on native tools not universally present. It will be an issue for a CI system to ensure these tools present on all build hosts as well in some other cases. -- 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

18 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3113) Problem when adding a new Object in unidirectional one-to-many and change the hashCode value of others objects of the collection

by Claudio (JIRA)

Problem when adding a new Object in unidirectional one-to-many and change the hashCode value of others objects of the collection ----------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3113 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3113 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6, 3.2.5 Environment: Hibernate Core 3.2.5.GA, Hibernate Annotations 3.3.0.GA and Hibernate EntityManager 3.3.1.GA Mysql Database 5.0 Reporter: Claudio Priority: Blocker Attachments: TestOneToMany.zip My application has two Entities: User and Phone. The User has a unidirectional one-to-many (join table) with Phone. The list of my classes: @Entity public class User implements Serializable { private static final long serialVersionUID = 0L; private Long id; private Set<Phone> phones = new HashSet<Phone>(); @Id @GeneratedValue(strategy=GenerationType.IDENTITY) public Long getId() { return id; } public void setId(Long id) { this.id = id; } @OneToMany(cascade = CascadeType.ALL, fetch=FetchType.EAGER) public Set<Phone> getPhones() { return phones; } public void setPhones(Set<Phone> phones) { this.phones = phones; } public void addPhone(Phone p){ if (phones.size()==0) { // Assert the first phone is main phone p.setMain(true); } else { // There are others phone if (p.isMain()){ // Remove the main of others phones for(Phone temp : phones){ temp.setMain(false); } } } phones.add(p); } public String toString(){ return "User - Set Phones: "+phones; } } @Entity public class Phone implements Serializable { private static final long serialVersionUID = 0L; private Long id; private String number; private boolean main; @Id @GeneratedValue(strategy=GenerationType.IDENTITY) public Long getId() { return id; } public void setId(Long id) { this.id = id; } public String getNumber() { return number; } public void setNumber(String number) { this.number = number; } public boolean isMain() { return main; } public void setMain(boolean main) { this.main = main; } // Overwrite equals public boolean equals(Object o){ if (this == o) return true; if (!(o instanceof Phone)) return false; Phone temp = (Phone)o; if (!number.equals(temp.getNumber())) return false; if (main != temp.isMain()) return false; return true; } // Overwrite hashCode public int hashCode(){ return 29 * number.hashCode() + 29 * (main?1:0); } } When I create the first Phone, call addPhone method of the User and persist the User, the code works. But when I create the second Phone and call addphone method of the User, the hashCode value of the first Phone change because of the overwrite of hashCode in Phone class. When I persist the User with two Phones, the Hibernate try to do two inserts in join table (User_Phone). But the one insert has been do in first persist of User. I got this Exception: Exception in thread "main" javax.persistence.RollbackException: Error while commiting the transaction at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:71) at test.Test.mergeUser(Test.java:23) at test.Test.main(Test.java:59) Caused by: org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:253) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:237) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:144) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:54) ... 2 more Caused by: java.sql.BatchUpdateException: Duplicate entry '1-1' for key 1 at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:1237) at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:936) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246) ... 10 more The Hibernate should do only one insert in table User_Phone. But it tries to do two inserts. It seems be a bug. I did a test code. It is attachment in Jira. I tried to run this code with Hibernate Core 3.2.5.GA and Hibernate Core 3.2.6.GA, but the problem occurs in both. -- 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

18 years, 1 month

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3126) Provide full support for one-to-many associations on a join table

by Gail Badner (JIRA)

Provide full support for one-to-many associations on a join table ----------------------------------------------------------------- Key: HHH-3126 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3126 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Gail Badner Assignee: Gail Badner There are gaps in functionality for one-to-many on join tables. This issue will contain subtasks for implementing full support. -- 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

18 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3137) SQLServerDialect: Schemaexport generates varchar columns for length>8000 which is not allowed in SQL Server

by Johannes Rudolph (JIRA)

SQLServerDialect: Schemaexport generates varchar columns for length>8000 which is not allowed in SQL Server ----------------------------------------------------------------------------------------------------------- Key: HHH-3137 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3137 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Environment: Microsoft SQL Server 2005 Reporter: Johannes Rudolph Priority: Minor Attachments: sqlserver.patch MS SQL Server allows varchar columns to be only a maximum of 8000 bytes long. With length>8000 you have to use the 'text' type in SQL Server < 2005 and from 2005 on 'varchar(max)'. Supplied a patch which fixes this. -- 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

18 years, 1 month

1
2
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 2008