Re: ec.deleteObject() and NSValidationErrors caused by the delete
Re: ec.deleteObject() and NSValidationErrors caused by the delete
- Subject: Re: ec.deleteObject() and NSValidationErrors caused by the delete
- From: Chuck Hill <email@hidden>
- Date: Thu, 25 Sep 2008 11:26:04 -0700
Hi joe,
On Sep 25, 2008, at 11:17 AM, Joe Little wrote:
I'm in the midst of doing some archival code. Once my objects are
copied off into their archival EOs, I then run this line:
ec.deleteObject(thisApplicant);
I get tons of exceptions based on NSValidationErrors, as various
foreign keys won't be satisfied. Example:
An Exception occured while trying to save the information:
com.webobjects.foundation.NSValidation$ValidationException: The
applicant property of Eval must have a Applicant assigned
My various delete rules in my model are all nullify. I'm presuming
that I need CASCADE instead to resolve the foreign key management? Or
is it simply a matter of changing the optionality to Optional from
Mandatory?
If deleting those objects is OK, then a CASCADE rule is what you
want. Otherwise, make the relationships optional. You will probably
need to update the nullity of the database columns too.
Chuck
--
Chuck Hill Senior Consultant / VP Development
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden