Re: Making a fake EO
Re: Making a fake EO
- Subject: Re: Making a fake EO
- From: Ken Anderson <email@hidden>
- Date: Thu, 19 Feb 2009 17:10:50 -0500
Just because there's a semantic on one object doesn't mean you need to
carry it over to another object.
Besides, if you need to know on the object in question whether a null
employee is a vacancy or an unavailable position, why not add a
boolean flag?
On Feb 19, 2009, at 5:00 PM, Gennady Kushnir wrote:
I don't want null because on the other object in my database that may
be related to some employee or unrelated to employee (with null
foreign key) and also it may be related to vacant employee place. So I
need some third option to indicate that aside from pointing to real
employee or null.
The other problem is that I am taking the list of employees from
external database that is in use by another application which is not
under my control. So it is undesirable to have that Mr. Vacancy in
official reports.
_______________________________________________
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