September 2012 - hibernate-issues

[Hibernate-JIRA] (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Steve Ebersole (JIRA)

11 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4468) Exception when using hibernate as JPA provider: "Found two representations of same collection"

by Håvard Nesvold (JIRA)

Exception when using hibernate as JPA provider: "Found two representations of same collection" ---------------------------------------------------------------------------------------------- Key: HHH-4468 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4468 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.3.2 Environment: 3.3.2.GA Reporter: Håvard Nesvold I have a J2SE application where I use JPA with Hibernate as persistence provider. The versions of the required hibernate jars that I use are: hibernate3.jar (3.3.2.GA) hibernate-annotations.jar (3.4.0.GA) hibernate-commons-annotations.jar (3.1.0.GA) hibernate-entitymanager.jar (3.4.0.GA) I have an entity where i have a bidirectional One-To-Many mapping. This is initialized to an empty list, something that clearly is allowed according to the JPA 1.0 spec. i.e. I have: in class Parent: @OneToMany(mappedBy="parent", cascade = CascadeType.ALL) private List<Child> children = ArrayList<Child>(); class Child: @ManyToOne @JoinColumn(name="PARENT_ID") private Parent parent; A certain sequence of actions result in a HibernateException being thrown (wrapped by JPA in a RollbackException): * Obtain a new EntityManager * Begin a transaction * Fetch a Parent entity from the entity manager (this exists in the db), call this e. * Apply an EntityManager.remove() on e * Commit the transaction * Begin a transaction * Apply an EntityManager.persist() on e * Commit the transaction The exception is thrown on the last commit(): Code: Caused by: org.hibernate.HibernateException: Found two representations of same collection: Parent.children at org.hibernate.engine.Collections.processReachableCollection(Collections.java:176) at org.hibernate.event.def.FlushVisitor.processCollection(FlushVisitor.java:60) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:124) ... I have tried to flush(), clear(), and pretty much everything on the entity manager (event fetching the Hibernate Sesssion and clearing this) - the only thing that helps is creating a new one before attempting the last transaction. Moreover, after some investigation, the persisted entity actually seems to be persisted correctly - despite the exception (this also seems to hold true for any cascaded persists), perhaps the only erroneous thing here is the fact that an exception is thrown when it really should not? -- 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

11 years, 8 months

2
7
0 / 0

[Hibernate-JIRA] (HHH-7371) Natural-id: ObjectNotFoundException when found entity is marked as deleted

by Strong Liu (JIRA)

11 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7371) Natural-id: ObjectNotFoundException when found entity is marked as deleted

by Strong Liu (JIRA)

11 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7570) Introduce flag to enable @FetchOverride for subclasses of "entity"

by Falko Modler (JIRA)

11 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Brett Meyer (JIRA)

11 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Brett Meyer (JIRA)

11 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] (BVAL-300) Clarify behavior of constructor validation in class hierachies

by Hardy Ferentschik (JIRA)

11 years, 8 months

3
5
0 / 0

[Hibernate-JIRA] Created: (ANN-808) @Enumerated(ORDINAL) does not work on VARCHAR columns

by Eduardo Costa (JIRA)

@Enumerated(ORDINAL) does not work on VARCHAR columns ----------------------------------------------------- Key: ANN-808 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-808 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Tested on Postgres, but the problem should be reproductible on any DB vendor Reporter: Eduardo Costa Copied from http://forum.hibernate.org/viewtopic.php?t=995698: ========== Suppose I have this enum: public enum Status { OK, NOK, NOT_APPLICABLE } And this property: @Column(name = "status") @Enumerated(EnumType.ORDINAL) private Status status; And this table (legacy, CANNOT be changed): CREATE TABLE tb_xxx ( id bigint NOT NULL, status character varying(1) NOT NULL, ) It leads to this exception: java.lang.IllegalArgumentException: No enum const class mypkg.Status.1 java.lang.Enum.valueOf(Enum.java:196) org.hibernate.type.EnumType.nullSafeGet(EnumType.java:110) Taking a look at EnumType.java, it is clear that Hibernate imposes ordinal stored as number and name stored as varchar. ========= IMHO, this is a "specification gap": JPA does not consider what to do if I'm trying to map a legacy enumerated value. Since I'm defining @Enumerated as "ordinal" and I have "0", "1", "2" on my database, I believe Hibernate should consider what I'm defining, not what an ancient DBA defined. Otherwise, I can't map this using only Hibernate Annotations/JPA (BTW, this code works with TopLink, only changing JPA provider on persistence.xml) -- 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

11 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6783) Using FetchType.EAGER with @ElementCollection results in multiple entity copies returned via Criteria query

by Greg Burcher (JIRA)

Using FetchType.EAGER with @ElementCollection results in multiple entity copies returned via Criteria query ----------------------------------------------------------------------------------------------------------- Key: HHH-6783 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6783 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.6.0 Environment: MySQL Reporter: Greg Burcher If we specify FetchType.EAGER on an @ElementCollection: @ElementCollection(fetch = FetchType.EAGER) @Column(name = "emailAddress") private Set<String> emailAddresses; then request all persisted objects of this class via Criteria: session.createCriteria(ReportSchedule.class).list(); The returned list contains multiple references to each ReportSchedule, one per email address. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

5
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2012