wood burning stoves 2.0
The moose likes Object Relational Mapping and the fly likes hibernate - insert object failed because of foreing key violation Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "hibernate - insert object failed because of foreing key violation" Watch "hibernate - insert object failed because of foreing key violation" New topic

hibernate - insert object failed because of foreing key violation

Lee Lifshits

Joined: Apr 17, 2008
Posts: 1
Hello all -
I have a a table events that generates it's primary key. This table has another table (insertion_string) that associated to it with a foreign key. My DB is postgres.

<class name="com.oversi.generated.generatedFiles.Events" table="events" schema="public">
<id name="eventId" type="long">
<column name="event_id" />
<generator class="sequence">
<param name="sequence">events_event_id_seq</param>
<set name="insertionsStrings" inverse="true" cascade="all-delete-orphan" fetch="select">
<column name="event_id" not-null="true" />
<one-to-many class="com.oversi.generated.generatedFiles.InsertionsString" />

When I try to insert a new event object I get the error :

insert or update on table "insertions_string" violates foreign key constraint "insertions_string_event_id_fkey"
Detail: Key (event_id)=(0) is not present in table "events".

I think this is because hibernate try to insert to the foreign key table (insertion_string) before inserting to the events table ( the one with the primary key)
Please help me to solve this
Mark Spritzler

Joined: Feb 05, 2001
Posts: 17276

You, try putting the inverse="true" into the InsertionsString side of the relationship.

This is a very common issue that everyone seems to have happen to them. It seems to be more logical that the inverse would be on the one side of a many to one, but to get what we expect, parents getting inserted before their children, requires the inverse="true" to be on the Many side of the relationship.

If you think of it this way, wherever you put the inverse, Hibernate will think, ok, so this is the same relationship that is modeled in the other side, and lets use that mapping as the controlling force of this relationship. So by having it in the Many side, it puts the parent in control of the relationship, since after all it is responsible for creating its children. Unless it is by immaculate conception.

[ April 17, 2008: Message edited by: Mark Spritzler ]

Perfect World Programming, LLC - iOS Apps
How to Ask Questions the Smart Way FAQ
I agree. Here's the link: http://aspose.com/file-tools
subject: hibernate - insert object failed because of foreing key violation
It's not a secret anymore!