On Jun 8, 2007, at 9:45 AM, David Avendasora wrote:
Ken and Chuck,
Thanks for the input. I have the delete rules set in the DB out of
habit. I usually make changes to the DB first, then to WO (as
opposed to generating SQL out of EOModeler) and it helps remind me
to setup the EOModel corr
Ken and Chuck,
Thanks for the input. I have the delete rules set in the DB out of
habit. I usually make changes to the DB first, then to WO (as opposed
to generating SQL out of EOModeler) and it helps remind me to setup
the EOModel correctly. It had just occurred to me that it may cause
c
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 oth
David,
Is there a reason you have them in your DB? It's far safer to
implement the cascade deletes in WO so you don't have to worry about
your object graph and the database getting out of sync.
To answer your question, the DB or WO will win at different times
because of the order of oper
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
