openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Johnson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-431) Order INSERT statements on joined subclasses from parent to child
Date Tue, 06 Nov 2007 19:05:50 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540529
] 

Nick Johnson commented on OPENJPA-431:
--------------------------------------

The suggestion given in OPENJPA-435 does result in the expected insert ordering.

> Order INSERT statements on joined subclasses from parent to child
> -----------------------------------------------------------------
>
>                 Key: OPENJPA-431
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-431
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 1.0.0
>            Reporter: Nick Johnson
>
> When creating a joined subclass relationship, it is desirable on the database side to
place an integrity constraint on the subclass table that its object_id must exist in the parent
class's table.  (Because the subclass's row cannot exist without the parent class's row.)
> Unfortunately, OpenJPA orders the inserts in the opposite direction, trying to insert
the child entity first (probably because that's the entity that the code is actually persisting),
so with the integrity constraint in place, the insert will fail.
> It would be nice if in a joined-subclass relationship where multiple inserts were needed,
SQL would be issued in order of highest in the class hierarchy to lowest so that integrity
constraints on the database won't be violated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message