One to One object ... but not in database

Question

I have many relationships which are truly one to one, however the defining primary key of the subbordinate table is the same as the primary key to the parent table.
In this scenario when mapped as a one to one in toplink, it doesn't know the order in which to add the records... it tries to add the subbordinate table's information first??? this results in a foreign key restraint.
Is there a correct way to handle this relationship in the toplink mappings? It seems like someone would have run across this before.

Answer 1

Yup... These threads have similar goals:
Re: Order of INSERT operations at commit time
Order of delete in unit of work
And here is the Javadoc that will address this:
http://otn.oracle.com/docs/products/ias/doc_library/90200doc_otn/toplink.903/tl_flapi/oracle/toplink/publicinterface/Descriptor.html#addConstraintDependencies(java.lang.Class)
- Don