Re: Delete rule "deny"
Re: Delete rule "deny"
- Subject: Re: Delete rule "deny"
- From: Kaspar Fischer <email@hidden>
- Date: Mon, 20 Jun 2005 10:39:40 +0200
Thanks a lot for your answer, Wade.
So does anybody know how one can prevent an object
from being deleted if the deletion would violate
(on an imaginary "Save" operation) a Deny rule?
What methods do I have to override?
Thanks again,
Kaspar
On 20.06.2005, at 10:27, email@hidden wrote:
I think you'll find this is a conscious design decision. It allows
you to delete the object and then replace it, or similar. If
validation were performed immediately, such manipulations would be
much more difficult.
A useful analogy is of a text field which has a formatter applied -
it'd be hell trying to type in a date [for example] if every subset
of the final date had to also be a valid date.
I'm afraid I'm just commenting on this though; I don't have a
practical workaround. I guess you'd have to implement some kind of
manual validation... in this case it's kind of a mechanism vs
policy abstraction - CoreData is your mechanism, and the policy you
want to apply is not an intrinsic part of that.
Wade Tregaskis (AIM/iChat, Yahoo & Skype: wadetregaskis, ICQ:
40056898, MSN: email@hidden, AV iChat &
email: email@hidden, Jabber: email@hidden)
-- Sed quis custodiet ipsos custodes?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden