Just wanted to check that this old issue still describes the situation properly:
http://issues.apache.org/jira/browse/OPENJPA-39
Cascade delete does not work with foreign key constraints
- marked as 'resolved - wont fix'.
Just wondering if maybe in the in-between time something has been impleme
Hi Adam -
JIRA-39 is pretty old. Possibly JIRA-1004 is related to your question? There
was recent discussion on this list about this.
Also there was recent mention on this list of using either one of these
settings regarding ordering of operations (reading the docs leaves me
with some questio
Hi Paul,
surely you don't mean http://issues.apache.org/jira/browse/OPENJPA-1004 ? Seems
completely unrelated.
I use both of these settings:
openjpa.jdbc.SchemaFactory=native(ForeignKeys=true)
openjpa.jdbc.MappingDefaults=ForeignKeyDeleteAction=restrict,
JoinForeignKeyDeleteAction=restrict
Hi Adam - Sorry if the reference was irrelevant.
Are you saying that CascadeType.REMOVE does not propagate through
multiple levels of OneToMany relations and this only happens when using
database foreign keys?
The SQL errors in JIRA-39 look like they might be due to operation
ordering - hen
Just a quick apology up-front because I haven't had time to follow up my problem
myself. I fully intend to at some point soon, but in the meantime, I am having
problems with cascading inserts, which I think may be closely related, so I
thought I'd add it into this thread.
I create a child and
