February 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-276) Support for CLOB not working for DB2 when table per concrete class is being used

by breako (JIRA)

Support for CLOB not working for DB2 when table per concrete class is being used -------------------------------------------------------------------------------- Key: EJB-276 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-276 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.1 Reporter: breako Hi, This came up in the forums: http://forum.hibernate.org/viewtopic.php?p=2344008#2344008 Sample code: Two Pojos @Entity public class Person { private int i; @Identity public int getI() { return i; } public void setI(int i){ this.i = i; } } @Entity public class Employee extends Person{ @Basic(fetch=FetchType.LAZY) @Lob public String getClobAttr() { return clobAttr; } public void setClobAttr(String clobAttr) { this.clobAttr = clobAttr; } } Simple test: public static void main (String args[]) { Query queryImpl = em.createQuery(" from Person"); List list = queryImpl.getResultList(); } This will generate SQL select person0_.clobAttr as clobAttr1 from (select nullif(0,0) as clobAttr from TPerson union all select clobAttr from TEmployee) person0_ which chucks the exception: DB2 SQL error: SQLCODE: -415, SQLSTATE: 42825, SQLERRMC: null I think the SQL hibernate should generate should be: select person0_.clobAttr as clobAttr1 from (select cast(null as CLOB) as clobAttr from TPerson union all select clobAttr from TEmployee) person0_ -- 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

13 years, 3 months

5
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-193) Publish javax.validation:validation-api to Maven central

by Pete Muir (JIRA)

Publish javax.validation:validation-api to Maven central -------------------------------------------------------- Key: BVAL-193 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-193 Project: Bean Validation Issue Type: Task Reporter: Pete Muir -- 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

13 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-200) Validator cannot find validation.xml unless is placed in /WEB-INF/classes/META-INF

by Cris Webber (JIRA)

Validator cannot find validation.xml unless is placed in /WEB-INF/classes/META-INF ---------------------------------------------------------------------------------- Key: BVAL-200 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-200 Project: Bean Validation Issue Type: Bug Components: ri-general - obsolete go to HValidator Environment: Java SE 1.5.0_10; Hibernate Validator 4.0.2.GA. Reporter: Cris Webber Priority: Minor Hibernate Validator requires that the validation.xml file is placed in the META-INF directory in order to load it. In the case of having a WAR file, placing the validation.xml file in /META-INF (at the same level as the WEB-INF directory) does not work, as Hibernate Validator cannot find the file there. Placing the file in /WEB-INF/classes/META-INF worked fine. I believe this is just a workaround and Hibernate Validator should be able to find validation.xml in /META-INF. -- 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

13 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3248) org.hibernate.cache.EhCache.toMap() throws NullPointerException

by Kenny MacLeod (JIRA)

org.hibernate.cache.EhCache.toMap() throws NullPointerException --------------------------------------------------------------- Key: HHH-3248 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3248 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.6 Reporter: Kenny MacLeod The toMap() method of org.hibernate.cache.EhCache is not null-safe. The expression cache.get( key ).getObjectValue() Will throw a NPE, since get(key) may return a null in cases where the key exists in the cache, but the value does not, e.g. if it has expired. This should either check for the null, or the list of keys should be obtained using getKeysWithExpiredCheck(), rather than just getKeys(). -- 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

13 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3747) Memory leak in EnumType class.

by Paweł Kępka (JIRA)

Memory leak in EnumType class. ------------------------------ Key: HHH-3747 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3747 Project: Hibernate Core Issue Type: Bug Components: core, metamodel Reporter: Paweł Kępka Priority: Critical Holding enum values in static enumValues map in EnumType class causes memory leaks on application server where hibernate is loaded by application server's common classloader (like for default configuration of JBoss4). SoftReference or SessionFactory based caching should be used instead. -- 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

13 years, 3 months

6
19
0 / 0

[Hibernate-JIRA] Created: (HHH-3836) composite-element with null columns in map is ignored

by Benoit Goudreault-Emond (JIRA)

composite-element with null columns in map is ignored ----------------------------------------------------- Key: HHH-3836 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3836 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.SP1 Environment: 3.3.0 SP1, noticed with Oracle and H2 but probably happens with all databases Reporter: Benoit Goudreault-Emond Attachments: patate.zip When a composite element with all properties set to NULL is inserted in a map of the said composite element, the data gets inserted to the database but is never retreived when reloading the entity. For instance, with an entity @Entity public class TestEntity { @Id private int id; @CollectionOfElements private Map<String, AccessPeriod> roleAccesses = new HashMap<String, AccessPeriod>(); // boilerplate getters/setters/etc omitted } And AccessPeriod being @Embeddable public class AccessPeriod { public Date startDate; public Date endDate; } If you insert in the map an AccessPeriod with both startDate and endDate set to null and persist the TestEntity, an entry is inserted in the auxiliary table, but when getting the TestEntity back, the map is empty. You get the same problem with a mapping file. This used to work in Hibernate 2.1--I found this out while porting some code to 3.3. See the attached example. You'll need to include Hibernate and h2 (com.h2database:h2 1.0.20061217) on your classpath to run it with the given jdbc.properties, but feel free to change it. -- 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

13 years, 3 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3318) Allow omitting varchar limit by default in PostgreSQL

by Luke Maurer (JIRA)

Allow omitting varchar limit by default in PostgreSQL ----------------------------------------------------- Key: HHH-3318 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3318 Project: Hibernate3 Issue Type: New Feature Components: core Environment: Hibernate 3.2.6, PostgreSQL 8.3.1 Reporter: Luke Maurer Priority: Minor Essentially, what I'd like is for a String without a given maximum length be mapped as a varchar or text rather than a varchar(255) as is now the case. The maximum doesn't do anything to improve performance or storage efficiency in PostgreSQL, so varchar(255) merely imposes an arbitrary constraint. It would be more idiomatic to use varchar where no limit is given, leaving varchar(n) for cases where the length is limited as a business rule rather than an implementation detail. (Naturally, one can always use @Lob where it's actually *important* that the column be a varchar or text. So this is definitely minor.) -- 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

13 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3244) Implement support NVARCHAR type

by Sergey Derugo (JIRA)

Implement support NVARCHAR type -------------------------------- Key: HHH-3244 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3244 Project: Hibernate3 Issue Type: New Feature Components: core Environment: al Reporter: Sergey Derugo JDBC 4.0 allows supports NVARCHAR type, but Hibernate doesn't handle it. Please implement support for NVarchar -- 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

13 years, 4 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2955) Unnecessary version updates in two cases.

by Sławomir Wojtasiak (JIRA)

Unnecessary version updates in two cases. ----------------------------------------- Key: HHH-2955 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2955 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: JDK 5.0 Reporter: Sławomir Wojtasiak Attachments: HibernateTest.zip I found two situations where hibernate generates unnecessary version updates. Let's illustrate it with a simple example: Session session = SessionFactory.getSession(); Transaction transaction = session.getTransaction(); transaction.begin(); Article a = new Article(); a.setName( "atricle" ); ********************************************* *** Quantity is the owner of the relation *** ********************************************* Quantity q = new Quantity(); q.setName( "quantity" ); q.setArticle( a ); a.getQuantities().add( q ); session.persist( a ); session.flush(); ***** Hibernate generates following SQLs ***** Hibernate: select nextval ('hibernate_sequence') Hibernate: select nextval ('hibernate_sequence') Hibernate: insert into Article (name, version, id) values (?, ?, ?) Hibernate: insert into Quantity (article_id, name, version, id) values (?, ?, ?, ?) ********************************************** a.getQuantities().clear(); session.flush(); *** Hibernate generates following SQLs *** Hibernate: update Article set name=?, version=? where id=? and version=? This update of version field is performed because collection of quantities is marked as dirty, but Article entity is not relation owner so nothing change in database after this clear. Should it works like this? It looks like a bug because database remain unchanged so version changing is unnecessary in my opinion. ****************************************** session.clear(); **** SECOND PROBLEM *** Now I generate true copy of persisted objects. Notice that I use HashSet instead of PersistSet which was set during persist operation. This operation is similar to merging objects prepared by SOAP, during communication with remote client for example. *********************** Article a1 = new Article(); a1.setId( a.getId() ); a1.setName( a.getName() ); a1.setVersion( a.getVersion() ); Quantity q1 = new Quantity(); q1.setArticle( a1 ); q1.setName( q.getName() ); q1.setVersion( q.getVersion() ); q1.setId( q.getId() ); a1.getQuantities().add( q1 ); a1 = (Article)session.merge( a1 ); session.flush(); ***** This operation generates following SQLs ***** Hibernate: select article0_.id as id0_1_, article0_.name as name0_1_, article0_.version as version0_1_, quantities1_.article_id as article4_3_, quantities1_.id as id3_, quantities1_.id as id1_0_, quantities1_.article_id as article4_1_0_, quantities1_.name as name1_0_, quantities1_.version as version1_0_ from Article article0_ left outer join Quantity quantities1_ on article0_.id=quantities1_.article_id where article0_.id=? Hibernate: update Article set name=?, version=? where id=? and version=? It looks like problem is located in replaceElements() method of CollectgionType class (or somewhere near it). Maybe I'm wrong but this collection was checked for changes during merge operation (See this select above.) so why it remains dirty if it contains the same data as database?. I checked this issue on other JPA implementations (OpenJPA for example) and version is not incremented after similar merge operation. ***************************************************** transaction.rollback(); -- 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

13 years, 4 months

3
2
0 / 0

[Hibernate-JIRA] Created: (EJB-318) PostUpdate callback not called after update on a collection / association (@OneToMany for example)

by Aghnar von Salza (JIRA)

PostUpdate callback not called after update on a collection / association (@OneToMany for example) -------------------------------------------------------------------------------------------------- Key: EJB-318 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-318 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Environment: Hibernate core3.2.5, entityManager 3.3.1, annotation 3.3.0, oracle 9i Reporter: Aghnar von Salza Environment is Weblogic 10 (J2EE 5), with Hibernate used as JPA provider There is no PostUpdate callback on an entity when one of its collections of other Entities (for example annoted with @OneToMany) is updated (i mean when one entity element is added or removed). JPA specification says that a postUpate must be called after the update of at least one data of an entity. I think we have to consider that a collection of other entities can be considered as 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

13 years, 4 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2010