Re: Help with complex db design concepts

From: drop the numbers <Paul>
Date: Thu, 09 May 2002 20:13:30 GMT
Message-ID: <>

In article <>, 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: (drop the numbers)
Received on Thu May 09 2002 - 22:13:30 CEST

Original text of this message