Re: Help with complex db design concepts

In article <57da7b56.0205091155.1f655f13_at_posting.google.com>, paul_geoffrey_brown_at_yahoo.com says...
>
> Why are you splitting the spatial objects up into so many tables?

        What if there are different attributes being tracked for different spatial entities?

        The other option would be a many-to-many with an Attribute entity that has an attribute type field and SpatialEntity, with that association table holding the value that goes with the linked attribute. This could be a dangerous design, though, if these values can be numbers, strings, etc., depending on the attribute used.

-- 

(Any opinions expressed are strictly mine only and not my employer's)
--------------------------------------------------------------------
Paul Tiseo, Intermediate Systems Programmer
Reply To: 123tiseo.paul_at_123mayo.edu (drop the numbers)