June 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4915) <list-index> base attribute ignored on insert for a bidirectional association (one-to-many)

by Olivier Lafontaine (JIRA)

<list-index> base attribute ignored on insert for a bidirectional association (one-to-many) ------------------------------------------------------------------------------------------- Key: HHH-4915 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4915 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-CR-1, 3.3.2 Environment: Hibernate 3.3.2GA and 3.5.0-CR-1 Oracle Database Reporter: Olivier Lafontaine Attachments: hibernate-poc-jira.zip My mapping looks like the following: {code:xml} <hibernate-mapping> <class name="Parent">  <list name="children" table="CHILD" cascade="all-delete-orphan"> <key column="ID_PARENT" not-null="true" /> <list-index base="1"> <column name="IDX" check="IDX > 0" /> </list-index> <one-to-many class="Child" /> </list> </class> <class name="Child">  <many-to-one name="parent" class="Parent" column="ID_PARENT" not-null="true" insert="false" update="false" /> </class> </hibernate-mapping> {code} As you can see from the mapping, we have a parent entity ({{Parent}}) referring child entities ({{Child}} using the {{children}} accessor). The index column ({{ORDER}}) is not an attribute in the child entity, so I referred to the second use case in section _6.3.3. Bidirectional associations with indexed collections_ of the reference guide to do my mapping. Everything works except for the index base, it is always 0 based on insert. I've tried both Hibernate 3.3.2GA and the latest development version (3.5.0-CR-1), the issue can be reproduced in both. I've joined a test case to reproduce the problem. While working on it, I realized there are updates after the inserts setting the correct index. However, we cannot change the database schema and there's a constraint on the index column enforcing a value > 0. So this issue is really important for us. I could manually handle the index values, but it would be so much easier to let Hibernate do it. I've traced the problem and it seems that {{StatefulPersistenceContext#getIndexInParent(..)}} does not considers the index base. Why are updates necessary after the inserts? It looks to me like Hibernate could correctly set the index parameter on the insert statements. -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5072) Invalid SQL produced when using FetchMode.SUBSELECT with SQLServerDialect

by kabram (JIRA)

Invalid SQL produced when using FetchMode.SUBSELECT with SQLServerDialect ------------------------------------------------------------------------- Key: HHH-5072 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5072 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Environment: Hibernate core 3.5, JPA 2.0, SQL Server 2005, JDK 1.6 Reporter: kabram Priority: Blocker I have a parent entity with child entities being loaded using SubSelect and eager fetching. I execute a query to retrieve all parents and get the following query which SQL Server 2005 does not support: select childtab0_.CONFIG_KEY as CONFIG5_23_1_, childtab0_.QUALIFIER as QUALIFIER23_1_, childtab0_.CONFIG_VALUE_ID as CONFIG1_1_, childtab0_.CONFIG_VALUE_ID as CONFIG1_24_0_, childtab0_.CONFIG_KEY as CONFIG5_24_0_, childtab0_.QUALIFIER as QUALIFIER24_0_, childtab0_.CONFIG_VALUE as CONFIG2_24_0_, childtab0_.IS_ENCRYPTED as IS3_24_0_, childtab0_.LIST_ORDER as LIST4_24_0_ from TEST_CHILD_TABLE childtab0_ where (childtab0_.CONFIG_KEY, childtab0_.QUALIFIER) in (select parenttab0_.CONFIG_KEY, parenttab0_.QUALIFIER from RSS_NEO_CANYON_CONFIG_KEY parenttab0_ ) order by childtab0_.LIST_ORDER asc SQL Server does not like the tuple in the where clause. -- 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, 9 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HCANN-30) EntityBinder: Incorrect WARN message about dynamicUpdate ("Entity used on a non root entity: ignored for...")

by Shahaf Abileah (JIRA)

EntityBinder: Incorrect WARN message about dynamicUpdate ("Entity used on a non root entity: ignored for...") ------------------------------------------------------------------------------------------------------------- Key: HCANN-30 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-30 Project: Hibernate Commons Annotations Issue Type: Bug Reporter: Shahaf Abileah Priority: Minor This my first bug so please excuse any mistakes I make in filing it, and help me correct them. I'm using PostgreSQL. I have a bunch of domain objects. Some of them are small class hierarchies. I chose to map each class hierarchy to a single table using a discriminator column. Here's one example where I have a base class (Note) and a subclass (TaskNote)... @Entity @org.hibernate.annotations.Entity(dynamicUpdate = true) @Table(name = "notes") @SequenceGenerator(name = "notes_note_id_seq", sequenceName = "notes_note_id_seq", allocationSize = 1) @Proxy(lazy = true) @Inheritance(strategy=InheritanceType.SINGLE_TABLE) @SQLDelete(sql="update notes set removed = true where note_id = ?") @DiscriminatorColumn( name=Note.noteTypeColumnName, discriminatorType=DiscriminatorType.INTEGER ) public abstract class Note implements Persistable { ... } @Entity @org.hibernate.annotations.Entity(dynamicUpdate = true) @Proxy(lazy = true) @DiscriminatorValue("1") public class TaskNote extends Note { ... } Notice that I added the following annotation to both: @org.hibernate.annotations.Entity(dynamicUpdate = true) I did this because I want to keep my updates lean. After adding this annotation I started seeing warnings in my log: 2010-11-01 10:03:22,210 WARN org.hibernate.cfg.annotations.EntityBinder @org.hibernate.annotations.Entity used on a non root entity: ignored for redfin.core.domain.TaskNote I spent some time experimenting with this annotation to understand how it works with class hierarchies. I discovered that: * If I put the annotation on the child class and not on the parent class, then I get the WARN but dynamicUpdate still works * If I put the annotation on the parent class and not the child class, then the WARN goes away but dynamicUpdate does not work * If I put the annotation on both, then the WARN is there and dynamicUpdate works To me this implies that the WARN is incorrect. Do you agree? I believe this is the code that is generating the message: http://www.docjar.com/html/api/org/hibernate/cfg/annotations/EntityBinder... Here are the particular versions of the various hibernate libraries that I'm using: <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator</artifactId> <version>3.0.0.ga</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate</artifactId> <version>3.2.7.ga</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-annotations</artifactId> <version>3.3.0.ga</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-commons-annotations</artifactId> <version>3.3.0.ga</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>antlr</artifactId> <version>2.7.5H3</version> </dependency> -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2666) subselect fetching ignores max results

by James Roper (JIRA)

subselect fetching ignores max results -------------------------------------- Key: HHH-2666 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2666 Project: Hibernate3 Issue Type: Improvement Components: query-hql, query-sql Affects Versions: 3.2.1 Environment: Hibernate 3.2.1 HSQLDB 8.0 Reporter: James Roper Priority: Minor When maxResults is set for a query, the hibernate subselect fetching strategy ignores it. For example, I have a class entry, that has a list of comments, which are configured to use the subselect fetching strategy. You can see that in the original query, only the top ? results are fetched: select top ? entry0_.id as id0_, entry0_.title as title0_, entry0_.entry as entry0_, entry0_.time as time0_, entry0_.category_id as category5_0_ from Entry entry0_ order by entry0_.time desc But then when it does the sub select query to lazily load the comments, this is the query it runs: select comments0_.entry_id as entry5_1_, comments0_.id as id1_, comments0_.id as id1_0_, comments0_.time as time1_0_, comments0_.comment as comment1_0_, comments0_.author as author1_0_ from Comment comments0_ where comments0_.entry_id in ( select entry0_.id from Entry entry0_ ) order by comments0_.time desc So, it loads every single comment in the database, even though only the comments for the top ? entries are needed. Of course, if there was no order by clause on the first query, the sub select may not return the same results, so it should probably only do this when there is an order by clause in the first query, and it should make sure it includes the order by clause in the sub select. -- 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, 9 months

6
12
0 / 0

[Hibernate-JIRA] Created: (ANN-609) Need a way to specify "unsaved-value" strategy using annotations

by Suji Suresh (JIRA)

Need a way to specify "unsaved-value" strategy using annotations ---------------------------------------------------------------- Key: ANN-609 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-609 Project: Hibernate Annotations Issue Type: Bug Environment: Hibernate 3.2.2, Hibernate-annotations 3.2.1 Reporter: Suji Suresh Hibernate has two ways of specifying a value for primary key: 1. Assign a value before handing it over to Hibernate 2. Have Hibernate generate the value before persisting In my project I have objects of both of the above specified types. In other words I assign value for the primary key for some the objects (lets call these objects "assigned") and for others I have Hibernate generate the value before persisting (lets call these objects "generated"). Since Hibernate annotations does not support "unsaved-value", I do not have a way of specifying "unsaved-value" strategy. While my "generated" objects work perfectly with Hibernate's default "unsaved-value" strategy, I see wrong (but expected) behaviour when I try to persist an "assigned" object that is already present in the database in that, I get StaleStateException instead of DataIntegrityViolationException -- 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, 9 months

6
9
0 / 0

[Hibernate-JIRA] Created: (HHH-6354) Implement natural ID mapping

by Gail Badner (JIRA)

Implement natural ID mapping ---------------------------- Key: HHH-6354 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6354 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Gail Badner Fix For: 4.0.0.next -- 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, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4815) Support orphan-removal for one-to-one inside component/@Embeddable

by Steve Ebersole (JIRA)

Support orphan-removal for one-to-one inside component/@Embeddable ------------------------------------------------------------------ Key: HHH-4815 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4815 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Steve Ebersole Fix For: 3.5 AFAICT this only makes sense for fk-based logical 1-1. See HHH-4726 for more details -- 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, 9 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-6351) Enum Bug when using OK word inside of a enum being retrieved

by Lucas Arruda (JIRA)

Enum Bug when using OK word inside of a enum being retrieved ------------------------------------------------------------ Key: HHH-6351 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6351 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.6.5, 3.3.0.GA Environment: Hibernate version 3.3.0.GA, 3.6.5.Final with hibernate-annotations 3.4.0.GA. Oracle database. Reporter: Lucas Arruda Priority: Minor I have a class with a field which is an enum, which is mapped by a enum called Status. The class is described (simplified and without all annotations) above: public class A { private Status status; public enum Status { OK, NOK, NAP } @Column(name = "STATUS") @Enumerated(EnumType.STRING) public Status getStatus() { return status; } ... } The thing is. I can store a record from A with status = 'OK', 'NOK' or 'NAP' perfectly. But, when I try to retrieve that record, if status = 'NOK' or 'NAP' it works correctly, but no with status = 'OK', which gives me an exception: java.lang.IllegalArgumentException: Unknown name value for enum class com.a.b.c.d.A$Status: OK at org.hibernate.type.EnumType.nullSafeGet(EnumType.java:113) ... Caused by: java.lang.IllegalArgumentException: No enum const class com.a.b.c.d.A$Status.OK at java.lang.Enum.valueOf(Enum.java:196) at org.hibernate.type.EnumType.nullSafeGet(EnumType.java:110) Reported a StackOverflow [1] and now one could solve this using 'OK' in the Enum. What I did to solve this, since I couldn't get I done with OK, was to change a little bit the enum with this, which works correctly: public enum Status { _OK("OK"), NOK("NOK"), NAP("NAP"); private String desc; public String getDesc() { return desc; } private Status(String desc) { this.desc = desc; } } Since I couldn't make it work with 'OK', I highly suspect it's either a big mistake by my part or a bug, so I'm reporting it. [1] http://stackoverflow.com/questions/6432933/hibernate-jpa-bug-not-recogniz... -- 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, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-764) ClassBridge and DynamicBoost should report affecting properties

by Sanne Grinovero (JIRA)

ClassBridge and DynamicBoost should report affecting properties --------------------------------------------------------------- Key: HSEARCH-764 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-764 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero currently when a ClassBridge or a DynamicBoost many optimizations are disabled (especially dirty checking to skip indexing) as we don't know which properties might affect the index state. If these interfaces could define the properties they are interested in explicitly, we could make some progress in the area of optimizations. -- 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, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3724) Bug in determining the getter method for property

by Senthil (JIRA)

Bug in determining the getter method for property -------------------------------------------------- Key: HHH-3724 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3724 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: hibernate-core-3.3.1.GA.jar, Oracle Express Edition 10g Reporter: Senthil Priority: Minor I have an entity class with a property "String nextOnError" mapping to the database column "varchar nextOnError". I have a getter method "String getNextOnError()" defined in the class. But I also have another method "boolean isNextOnError()" for my other processing in the application. I was expecting hibernate would pick the getter method "String getNextOnError()" as the getter method but it is not. It is always picking the "boolean isNextOnError()" and resulting in "Class cast exception: java.lang.Boolean" during insertion. This is because, for each property, in the class "org.hibernate.property.BasicPropertyAccessor", the method "getterMethod(Class theClass, String propertyName)" is looping through all the getter methods with no arguments. The loop breaks when it finds any method starts with either "isNextOnError()" or "getNextOnError()". Unfortunately, in my case, it always ends up with "boolean isNextOnError()". I think the correct way is to check all the methods for starting with get... and if nothing is found, then start looking for method starting with 'is...' . Thanks. -- 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, 9 months

3
5
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 June 2011