I've got some problem due to foreign key during the creation of object.
I've got two classes House and Flat. Flat extend House. Both have the same identity, the field called "reference". Flat.reference is also a foreign key to House.
When i create a object Flat an error occur because the foreign key is not respected.
It seems to be logic that when trying to insert an object Flat the part of Flat corresponding to the object House must be first insert so the foreign key is respected. But it seems that castor don't do that and first try to insert in the table representing Flat first.
To avoid this I have try to defer all the foreign key check in postgresql a the end of the transaction but it didn't change anything.
Can I have confirmation of this behaviour or big limitation.
Thanks
Julien
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
