Does your data haphazardly point to any location? Or does it point
always to city (the most discreet) which is hierarchical down from
Country?
If that is the case just point it to city and you will have access to
all the other locations as they would all be joined in to-one
relationship up the tree.
Otherwise, maybe have an intermediary object that has a type attribute.
HTH
James Cicenia
On Apr 20, 2008, at 8:15 PM, Mr. Frank Cobia wrote:
I have a database design question. I am posting it to the WebObjects
list because I am building a WebObjects app and want a solution that
works well for EOF.
I have a table of data that has to have a location associated with
it. Unfortunately the level of the location is not constant. The
data can be associated with a Country, Region, State, Metro Area,
County or City. Each of those levels is its own table with
relationships pointing to the related locations. i.e. a State knows
which Region it belongs to and which Metro Areas belong to it.
I have been unable to come up with a design that seems elegant. I
have thought of having 6 separate relationships to each of the
location levels, but it seems to duplicate data and the data could
get out of sync if a state is moved to a different region or a City
is moved to a different county.
Has anyone had a situation like this and come up with a good solution?
Thanks,
Frank Cobia
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/james%40jimijon.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
