August 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4107) Many-to-one, one-to-many with lazy=true and combined primary key(@JoinColumns) leads to infinite look when doing session.load(.. or session.get(..

by ulf thoresen (JIRA)

Many-to-one, one-to-many with lazy=true and combined primary key(@JoinColumns) leads to infinite look when doing session.load(.. or session.get(.. -------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-4107 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4107 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.x Environment: Hibernate version 3.2.1.ga, Oracle 10.1.3, jdbc driver= 10.2.0.4 Reporter: ulf thoresen Priority: Critical I have one-to-many from Class1with fetch type lazy. In Class2 I have have a Embedded primary key with the many-to-one on the key. When I try to load og get Class1 I get a infinite loop that prints out a stack of selects. It all ends with a ava.lang.StackOverflowError. I will put in a example... -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-210) XML constraint declaration with missing mandatory elements throws IllegalArgumentException insteadof ValidationException

by Hardy Ferentschik (JIRA)

XML constraint declaration with missing mandatory elements throws IllegalArgumentException insteadof ValidationException -------------------------------------------------------------------------------------------------------------------------- Key: HV-210 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-210 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.0.0.Beta3 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.CR1 -- 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

16 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-176) Return the list of matching ConstraintDescriptor for a given set of groups

by Emmanuel Bernard (JIRA)

Return the list of matching ConstraintDescriptor for a given set of groups -------------------------------------------------------------------------- Key: HV-176 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-176 Project: Hibernate Validator Issue Type: New Feature Components: engine Affects Versions: 4.0.0.Beta1 Reporter: Emmanuel Bernard -- 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

16 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HV-209) Correctly handle <valid> configured in xml

by Hardy Ferentschik (JIRA)

Correctly handle <valid> configured in xml ------------------------------------------ Key: HV-209 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-209 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.0.Beta3 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.CR1 We have to make sure that: - <valid> nodes gets properly picked up and applied - @Valid gets ignored when the field/getter in xml has ignore-annotations set to true -- 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

16 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (EJB-462) 3.5.beta1: Wrong query generation for @EmbeddedId and @MappedById

by Juergen Zimmermann (JIRA)

3.5.beta1: Wrong query generation for @EmbeddedId and @MappedById ----------------------------------------------------------------- Key: EJB-462 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-462 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.5 Environment: Hibernate 3.5.beta1 Reporter: Juergen Zimmermann I'm having this entity class: @Entity @Table(name="reklamation") @NamedQueries({ @NamedQuery(name = "findReklamationenByKundeId", query = "SELECT r FROM Reklamation r WHERE r.bestellung.kunde.id = :kundeId ORDER BY r.bestellung.id") }) public class Reklamation implements Serializable { @EmbeddedId @AttributeOverride(name="bestellungId", column=@Column(name="bestellung_fk")) private ReklamationId id = new ReklamationId(); @MappedById("bestellungId") @ManyToOne private Bestellung bestellung; ... @Embeddable public static class ReklamationId implements Serializable { public Long bestellungId; public Date datum; } } The owner class: @Entity @Table(name="bestellung") @NamedQueries({...}) public class Bestellung implements java.io.Serializable { @Id @GeneratedValue(strategy=AUTO, generator="bestellung_sequence_name") @SequenceGenerator(name="bestellung_sequence_name", sequenceName="bestellung_b_id_seq", allocationSize=1) @Column(name="b_id", unique=true, nullable=false, precision=20) private Long id = null; ... } The table definitions in PostgreSQL: CREATE TABLE reklamation( bestellung_fk BIGINT NOT NULL, datum DATE NOT NULL, ... PRIMARY KEY(bestellung_fk, datum), FOREIGN KEY (bestellung_fk) REFERENCES bestellung(b_id) ); CREATE TABLE bestellung( b_id BIGSERIAL NOT NULL PRIMARY KEY, kunde_fk BIGINT NOT NULL, ... FOREIGN KEY (kunde_fk) REFERENCES kunde(k_id) ); The wrong generation of SQL regarding @EmbeddedId and @MappedById: 2009-08-22 09:04:06,469 DEBUG org.hibernate.SQL - /* named HQL query findReklamationenByKundeId */ select reklamatio0_.bestellung_fk as bestellung1_34_, reklamatio0_.datum as datum34_, reklamatio0_.bestellung_b_id as bestellung4_34_, reklamatio0_.inhalt as inhalt34_ from reklamation reklamatio0_, bestellung bestellung1_ where reklamatio0_.bestellung_b_id=bestellung1_.b_id and bestellung1_.kunde_fk=? order by reklamatio0_.bestellung_b_id -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4106) SQLStateConverter treats SQLServer snapshot isolation exception as a SQLGrammarException

by Anders Wallgren (JIRA)

SQLStateConverter treats SQLServer snapshot isolation exception as a SQLGrammarException ---------------------------------------------------------------------------------------- Key: HHH-4106 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4106 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: SQL Server 2008, SQL Server 2005, jtds 1.2.2 JDBC driver Reporter: Anders Wallgren A SQLException thrown due to a snapshot isolation conflict gets treated as a SQLGrammarException The SQLState is S0005 and the vendorCode is 3960. The error message is: Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table 'dbo.XXX' directly or indirectly in database 'XYZ' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement. This should be turned into an optimistic locking exception, or something like 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

16 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1803) Allow fetching with criteria when scrolling

by Sam Doyle (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1803?page=c... ] Sam Doyle commented on HHH-1803: -------------------------------- I have confirmed the bug on 3.3.2.GA but unfortunately the patch did not work in my case. Originally I had thought this was a problem with Hibernate Search and as the previous commenter stated this has a serious impact to Hibernate Search indexing performance. > Allow fetching with criteria when scrolling > ------------------------------------------- > > Key: HHH-1803 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1803 > Project: Hibernate Core > Issue Type: Improvement > Components: query-criteria > Affects Versions: 3.2.0.cr2 > Reporter: Maarten Winkels > Attachments: Child.java, criteria-scroll-fetch-collection.patch, CriteriaScrollFetchTest.java, Parent.java, ParentChild.hbm.xml > > > When querying by criteria, fetching is allowed, but when scrolling a criteria, the fetching corrupts the result. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-1139) Create joined subclass for constrained 1:1 foreign key

by Charles Honton (JIRA)

Create joined subclass for constrained 1:1 foreign key ------------------------------------------------------ Key: HBX-1139 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1139 Project: Hibernate Tools Issue Type: New Feature Components: reverse-engineer Affects Versions: 3.2.4 Beta1 Reporter: Charles Honton Attachments: join_subclass.patch Create a joined subclass for a 1:1 foreign key constrained by primary key on each side of relationship. Retain generation of 1:1 if foreign key has non-primary key on one or both sides of relationship -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-1138) EntityPOJOClass.getInverseProperty() provides the inverse property for all different relationship types

by Charles Honton (JIRA)

EntityPOJOClass.getInverseProperty() provides the inverse property for all different relationship types ------------------------------------------------------------------------------------------------------- Key: HBX-1138 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1138 Project: Hibernate Tools Issue Type: New Feature Components: reverse-engineer Affects Versions: 3.2.4 Beta1 Reporter: Charles Honton Priority: Minor Attachments: inverse_property.patch Provide a method which the pojo templates can use to obtain the inverse property for any relationship. The attached patch also improves current inverse finding methods by matching the table of the columns as well as the column name. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-1137) OneToOne is assigned improper table for FOREIGN_KEY_FROM_PARENT constraints

by Charles Honton (JIRA)

OneToOne is assigned improper table for FOREIGN_KEY_FROM_PARENT constraints --------------------------------------------------------------------------- Key: HBX-1137 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1137 Project: Hibernate Tools Issue Type: Bug Components: reverse-engineer Affects Versions: 3.2.4 Beta1 Reporter: Charles Honton Priority: Minor Attachments: proper_1-1_table.patch org.hibernate.cfg.JDBCBinder.bindOneToOne() creates OneToOne with improper containing table when called with the target table of foreignKey.getReferencedTable(). -- 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

16 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2009