January 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5880) Gradle has to deploy testing artifacts

by Sanne Grinovero (JIRA)

Gradle has to deploy testing artifacts -------------------------------------- Key: HHH-5880 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5880 Project: Hibernate Core Issue Type: Task Components: build Reporter: Sanne Grinovero Assignee: Hardy Ferentschik Priority: Minor Fix For: 4.0.0.Alpha1 The <groupId>org.hibernate</groupId><artifactId>hibernate-testing</artifactId> artifact is not created nor deployed to maven repository -- 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, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5648) Auto-increment IDs should be assigned upon commit (or hooks made available)

by Wallace Wadge (JIRA)

Auto-increment IDs should be assigned upon commit (or hooks made available) --------------------------------------------------------------------------- Key: HHH-5648 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5648 Project: Hibernate Core Issue Type: Bug Components: core Environment: v3.6, mysql Reporter: Wallace Wadge The connection pool BoneCP (http://jolbox.com) has support to automatically replay a transaction when a database/network goes down. Under hibernate, since objects get their IDs populated upon INSERTs, the following sequence of events is possible: BEGIN TRANSACTION INSERT STATEMENT (object gets the ID field populated) => network goes down, new connection is given and transaction is replayed beneath hibernate COMMIT TRANSACTION Now the database has given us a new ID but hibernate never had a chance to update the object properly. To fix: either assign the IDs upon a successful transaction commit or at least provide some kind of hooking mechanism so as to correct the problematic objects. -- 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, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HV-376) validateValue() and validateProperty() are too restrictive regarding processable property names

by Gunnar Morling (JIRA)

validateValue() and validateProperty() are too restrictive regarding processable property names ----------------------------------------------------------------------------------------------- Key: HV-376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-376 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Final Reporter: Gunnar Morling Assignee: Hardy Ferentschik Priority: Minor The methods Validator#validateValue() and Validator#validateProperty() expect the name of a bean property, for which constraint validation should be performed. Currently not all valid Java property (field/method) identifiers are supported here, as the specified property name is processed in PathImpl with a regular expression, that matches only the word character class (A-Za-z0-9_), causing the evaluation of uncommon but yet valid property names such as the following ones to fail: * private String höchstBetrag; // German Umlaute such as "ö" are allowed in Java identifiers * private String €Amount; // some currency signs such as "€" are allowed, sigh * private String höchst\u00f6Betrag; // specifying letters such as "ö" using Unicode is allowed Trying to do so results in the following exception: {code:java} java.lang.IllegalArgumentException: Unable to parse property path ö at org.hibernate.validator.engine.PathImpl.parseProperty(PathImpl.java:216) at org.hibernate.validator.engine.PathImpl.createPathFromString(PathImpl.java:64) at org.hibernate.validator.engine.ValidatorImpl.validateValue(ValidatorImpl.java:152) {code} More information on the identifiers allowed in the Java language can be found in [JLS, chapter 3.8|http://java.sun.com/docs/books/jls/third_edition/html/lexical.html#3.8]. -- 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, 1 month

3
8
0 / 0

[Hibernate-JIRA] Created: (HV-415) Rename validateParameters to validateAllParameters

by Emmanuel Bernard (JIRA)

Rename validateParameters to validateAllParameters -------------------------------------------------- Key: HV-415 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-415 Project: Hibernate Validator Issue Type: Improvement Affects Versions: 4.2.0.Beta1 Reporter: Emmanuel Bernard I got confused by validateParameter vs validateParameters I think changing the name to validateAllParameters will solve the issue. -- 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, 1 month

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5057) ScrollableResults does not fetch many-to-many collections

by Jérôme Van Der Linden (JIRA)

ScrollableResults does not fetch many-to-many collections --------------------------------------------------------- Key: HHH-5057 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5057 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Jérôme Van Der Linden Priority: Blocker I have a many-to-many relation between two objects : {code:title=Project.java|borderStyle=solid} @Entity public class Project { private List<Viperson> managers; @ManyToMany(targetEntity = Viperson.class) @JoinTable(name = "PRJMANAGER", joinColumns = @JoinColumn(name = "PROJECTID", nullable = false), inverseJoinColumns = @JoinColumn(name = "VIPID", nullable = false)) public List<Viperson> getManagers() { return managers; } } {code} {code:title=Viperson.java|borderStyle=solid} @Entity public class Viperson { private List<Project> projects; @ManyToMany(mappedBy = "managers", targetEntity = Project.class) public List<Project> getProjects() { return projects; } } {code} And the following test (actually, it is a code from spring batch HibernateCursorItemReader I put in a testcase) : {code} @Test public void testSelectAll() { StatelessSession statelessSession = sessionFactory.openStatelessSession(); ScrollableResults cursor = statelessSession.createQuery("from Project").scroll(); Object[] data = null; if (cursor.next()) { data = cursor.get(); } } {code} data contains a {{Project}} but {{managers}} field is *null*, +even if I add eager fetching+. I have also a {{OneToMany}} in the {{Project}} class. This one is well loaded (i have a {{PersistentBag}}). Is there anything I miss ? I suspect a bug on that. -- 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, 1 month

3
3
0 / 0

[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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

1
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2011