Re: Modeling Address using Relational Theory

I was hoping to hear from you on this one, Marshall. Do you agree that defining something as a list, even if using no insert or delete operators on it, has advantages over manually enumerating the list values using attribute names that have ordering information in them and then coding the logic for the order in the application code?

Do you still think that addressLine1, addressLine2, each single-valued is a better approach than addressLines that is a multivalued list? Is that because there are only two values in this list? If there were 15, would it still be the best approach?

Since you are a list advocate but work more in the relational world than I, any light you can shed on this one case of the "address" attributes would be most helpful. And, of course, others are welcome to jump in too.

--dawn Received on Sun Sep 04 2005 - 14:36:15 CEST