On Jun 8, 2007, at 8:57 AM, David Avendasora wrote:
Hi all,
I have a question regarding the best place to handle cascading
deletions. Right now both my database (MS SQLServer) and my EOModel
have cascading deletes defined on several relationships. The
EOModel and database mirror each other's cascade settings.
Is this going to confuse WO if it goes to delete a related object
only to find that the DB has already deleted it (I'm assuming that
the database will have deleted the related record before WO gets
around to it)?
I would not do this. It is EOF's job to maintain object graph
integrity. As long as the cascades are in the model and match the
DB it is not likely to confuse EOF. But you may get database
exceptions as the transaction will have explicit deletes for rows the
database will cascade delete.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
