February 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-843) Version increment not triggered on @OneToOne property modification having inverse owner

by Guenther Demetz (JIRA)

Version increment not triggered on @OneToOne property modification having inverse owner --------------------------------------------------------------------------------------- Key: ANN-843 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-843 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate 3.3.1.GA , Microsoft SQL Server Reporter: Guenther Demetz Priority: Minor Attachments: Testcase.jar In the revised "Java Persistence with Hibernate" book by Christian Bauer and Gavin King on page 464 there's written following about versioning: "If you use Hibernate as JPA provider ... every value-typed property modification .. triggers a version increment." Now I saw that Version increment indeed is not triggered on @OneToOne properties having an inverse owner (= mappedBy setted). This allows several concurrent transactions to set the association from same object towards different targets without having a OptimistickLockException at commit. This violates the ToOne policy! (Hibernate detects the inconsistency later when loading the property from database: org.hibernate.HibernateException: More than one row with the given identifier was found) Please see attached junit-testcase for reproducing the problem. regards Guenther Demetz -- 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

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-428) Java 1.6 specific method used in programmatic validation API

by Christian Quanz (JIRA)

Java 1.6 specific method used in programmatic validation API ------------------------------------------------------------ Key: HV-428 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-428 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Beta1, 4.1.0.Final, 4.1.0.CR1, 4.1.0.Beta2, 4.1.0.Beta1 Environment: Java 1.5.0 (IBM J9 2.3); Hibernate Validator 4.1.0.FINAL Reporter: Christian Quanz In ValidationFactoryImpl class, the method addProgrammaticConfiguredConstraints(...) uses the Java 1.6 specific java.lang.String method isEmpty(). Thus, the programmatic API currently cannot be used in a Java 1.5 setting. -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5830) Improve LOB Type handling

by Steve Ebersole (JIRA)

Improve LOB Type handling -------------------------- Key: HHH-5830 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5830 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.1 3.6 introduced the new approach for defining Type, both in the use of delegated descriptors as well as the introduction of a {{TypeRegistry}}. There were specific problems caused in regards to handling large string and binary ({{BLOB}}, {{LOB}}, {{LONGVARCHAR}}, {{LONGVARBINARY}}) SQL types. Generally speaking these all boil down the need for dialects to be able to define specific, appropriate "{{Type}} overrides". This is planned for 4.0, but we need to account for something similar in 3.6 as well. -- 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
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4617) Using blobs with hibernate causes error

by Radosław Smogura (JIRA)

Using blobs with hibernate causes error --------------------------------------- Key: HHH-4617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4617 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2 Environment: Hibernate 3.5-b2, Glassfish v3 promoted build 74, PostgreSQL 8.3.7 Reporter: Radosław Smogura Priority: Critical I have entity with byte[] property annotated as @Lob and lazy fetch type, when table is createad the created column is of type oid, but when the column is read in application, the Hibernate reads the OID value instead of bytes under given oid. It's behavior like to read / write bytea. If i remember well, auto-creating table with Hibernate creates oid column. The proper behavior for dealing in PostgreSQL (and this behavior is in Hibernate 3.4) is to use oids. -- 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

4
16
0 / 0

[Hibernate-JIRA] Created: (HHH-5163) ClassCastException when Hibernate tries to cache results using ResultTransformer

by Strong Liu (JIRA)

ClassCastException when Hibernate tries to cache results using ResultTransformer -------------------------------------------------------------------------------- Key: HHH-5163 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5163 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Reporter: Strong Liu Assignee: Gail Badner Fix For: 3.5.x, 3.6 When Hibernate executes a cacheable query using a ResultTransformer, it will attempt to cache the results AFTER applying the ResultTransformer. The problem is that the ResultTransformer may modify the data in a way that Hibernate won't understand it anymore, and in this case it will generate a ClassCastException when trying to cache it. --------------------------- this can be reproduced by CriteriaQueryTest with following change: papa-pc:testsuite stliu$ svn diff src/test/java/org/hibernate/test/criteria/CriteriaQueryTest.java Index: src/test/java/org/hibernate/test/criteria/CriteriaQueryTest.java =================================================================== --- src/test/java/org/hibernate/test/criteria/CriteriaQueryTest.java (revision 19246) +++ src/test/java/org/hibernate/test/criteria/CriteriaQueryTest.java (working copy) @@ -613,6 +613,7 @@ ) .addOrder( Order.desc("studentName") ) .setResultTransformer( Transformers.aliasToBean(StudentDTO.class) ) + .setCacheable( true ) .list(); assertEquals(2, resultWithAliasedBean.size()); -- 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

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-5879) Expose state from AbstractEntityPersister / Type / SessionFactoryImplementor for OGM usage

by Emmanuel Bernard (JIRA)

Expose state from AbstractEntityPersister / Type / SessionFactoryImplementor for OGM usage ------------------------------------------------------------------------------------------- Key: HHH-5879 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5879 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.6.0 Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.6.1 -- 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

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5569) Hibernate should not use LONG type for Oracle

by Mindaugas Žakšauskas (JIRA)

Hibernate should not use LONG type for Oracle --------------------------------------------- Key: HHH-5569 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5569 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Environment: 3.5.0.Beta-1, Oracle 9i Reporter: Mindaugas Žakšauskas This is a spin-off from http://stackoverflow.com/questions/3719905/why-has-hibernate-switched-to-.... With the changes introduced in HHH-3892 Hibernate started to use Oracle LONG type instead of CLOB for properties of type="text". This is a bad idea because of the following: * it creates huge amount of pain for people who depend on Hibernate automatically creating table structure for them. Tables created with the same mapping will have different structure than tables created with earlier version of Hibernate * Oracle LONG type has a limitation: there can be _only one_ column of this type within a single table; * Oracle has deprecated LONG type many years ago and advised against using this type ever since 8i. See http://www.orafaq.com/wiki/LONG. Defining a property to have type="clob" is not really a solution; other databases might have other, more suitable types to store this type of data (not necessarily CLOB). At the moment the only workaround is to define custom dialact and use it; but this is a very poor solution in the long term. -- 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
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-879) Enable joining the same association twice with Criteria

by Ashkan Aryan (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-879?page=co... ] Ashkan Aryan commented on HHH-879: ---------------------------------- With regards to Simon's suggestion above, it does work, however there are a couple of issues you need to take into account while implementing it. Here's an example of how I did it. relationship : ClassA- 1 : 0...* -ClassB Assuming that you already have a criteria for ClassA, called classACriteria, you will need to add something like this to it: {code:title=sample|borderStyle=solid} Conjunction conjunction = Restrictions.conjunction(); DetachedCriteria detachedCriteria1 = DetachedCriteria.forClass(ClassA.class).setProjection(Projections.id()); detachedCriteria1.createAlias("classB", "classBAlias1"); //classB is the name of property representing a bag of ClassA instances in ClassB detachedCriteria1.add(Restrictions.eq("classBAlias1.field1", value1)); //Replace field one with the appropriate property name detachedCriteria1.add(Restrictions.eq("classBAlias1.field2", value2)); // DetachedCriteria detachedCriteria2 = DetachedCriteria.forClass(ClassA.class).setProjection(Projections.id()); detachedCriteria2.createAlias("classB", "classBAlias2"); detachedCriteria2.add(Restrictions.eq("classBAlias2.field3", value3)); detachedCriteria2.add(Restrictions.eq("classBAlias2.field4", value4)); conjunction.add(Property.forName("id").in(detachedCriteria1)); conjunction.add(Property.forName("id").in(detachedCriteria2)); classACriteria.add(conjunction); {code} Please note, you'll have to specifically set the projection on each criteria (in this case we're assuming that ClassB has a unique identifier) otherwise you'll get a nasty NPE. As mentioned before this is not ideal (a proper join would've been preferable in terms of performance) but at least it works! > Enable joining the same association twice with Criteria > ------------------------------------------------------- > > Key: HHH-879 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-879 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Vladimir Bayanov > > Make double joining the same association with Criteria.createCriteria possible. See: http://forum.hibernate.org/viewtopic.php?t=931249 -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2011