Hi,
> using <property name="openjpa.jdbc.SchemaFactory"
> value="native(ForeignKeys=true)"/> but
> we use custom data types in our schema that weren't being properly
> validated... so that wasn't really > an option for me.

> Sometimes though, everything works as it should and nothing goes wrong.

Without reading the existing foreign key information, OpenJPA will not be
able to reorder the SQL it issues to satisfy the database constraints. The
suggestion choice is
1. to instruct OpenJPA *not* to reorder the SQL or rather follow the order
in which object operations were performed
  <property name="openjpa.jdbc.UpdateManager" value="operation-order">
2. perform the object operations in a order that satisfy the foreign key
constraints (such as inserting a parent before a child)

--
Sent from the OpenJPA Users mailing list archive at Nabble.com.