Re: Inherited Relationships using Different Destinations
Re: Inherited Relationships using Different Destinations
- Subject: Re: Inherited Relationships using Different Destinations
- From: Florijan Stamenkovic <email@hidden>
- Date: Fri, 05 Sep 2008 14:52:47 -0400
On Sep 05, 2008, at 13:56, Chuck Hill wrote:
What you need, and want, IMHO, is a different relationship.
This was exactly what I thought when I first dived into what Dave was
saying. Then I thought, yeah, but then he would not be able to just
generically call somePart.lotCode() and get the right thing. Then I
thought, if he does it generically, he looses his NSArrays being
parameterized with the proper subclass, so what's the point in the
first place??? Which made me conclude that Dave is overdoing the
"model after real life" concept (it's not life, it's sw). Then I
though, well, f*** it, I'll go do some real work and just make a
comment on the bizarreness of this attempt.
And since you say you are more worried about setting the getting,
well, that's easy:
public void validatePart(...){
// is this Part relatable with this LotCode? No? throw an NSVal.ValEx!
}
Or even
public void setPart(...){
// if not the right subclass of Part, well, throw exception or
ignore or whatever
}
I mean, I doubt you can get your GUI to recognize all the overriding
you did in the model anyway, so at some point in the GUI you need to
remove unacceptable choices so the user can not screw up, and if you
do that, well, then you might as well put a hard-core stop on any
mistake by throwing an exception. What you are doing now seems
incredibly more complicated, and less secure really.
It was a nice thought though. Really, really out there...
You can't just willy nilly change things.
Like hell you can't... It's really quite easy too, I mean, that is
partly the reason we sit around emailing each other, no? :-P
F
_______________________________________________
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