Issue Type: Bug Bug
Affects Versions: 4.1.8
Assignee: Unassigned
Attachments: stacktrace.txt
Components: entity-manager
Created: 07/Feb/13 7:14 AM
Description:

Since the upgrade to Hibernate 4.1.9 (previously 4.1.7) we're getting constraint violations against the primary keys. Reverting to 4.1.7 solves the problem. I've been trying many things to isolate the problem.

This is happening with both mysql and derby. I'm including the stack traces into this ticket.

Our entity model is very extensive, so I'm unable to provide test code at this moment. But if somebody can talk me through what other things I can check. I've run out of options. :-/

=====================================

What might help is the common superclass of all our entities. Maybe it's something with the id table ?

@Indexed
@Table(name = "ENTITIES")
@Entity
@org.hibernate.envers.Audited
@Inheritance(strategy = InheritanceType.JOINED)
public abstract class LongIdEntity implements Serializable { @Id @GeneratedValue(strategy = GenerationType.TABLE) private Long id; .... }

Environment: Linux x64, Java 1.7.0b11, Maven 3.x, Spring 3.x
Project: Hibernate ORM
Labels: jpa2 hibernate core
Priority: Major Major
Reporter: Jan Goyvaerts
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira