Re: More on lists and sets

From: David Cressey <>
Date: Sun, 26 Mar 2006 18:58:36 GMT
Message-ID: <wvBVf.1871$Po1.1363_at_trndny01>

[Quoted] "dawn" <> wrote in message

> RM and other models. But the reason is that the RM claims the
> exclusivity with the Information Principle. If a data model has a big

I don't think the Information Principle means "exclusivity" in this sense.

> enough umbrella to permit composite structures other than relations,
> then it seems that it is no longer the RM, right?

It depends. A data structure can be "simple" in a relational sense, but "composite" in some other sense.

VARCHAR is simple from the point of view of all the realtional operators. It's composite from the point of view of the substring operator (or function).

I favor relational design where column domains are simple from a relational standpoint. But I don't object to the existence of a substring function embedded in the SQL.

> So, I am more than willing to agree that relations (e.g. functions) are
> a good structure for modeling data, but I want lists too. It sounds
> like we agree on this point, perhaps?
We can coexist.

If you want to treat the set of toppings on a pizza as a list in "your" program, go ahead.
If I want to treat it as a set in "my" database it's not up to you to be offended, or disappointed, or to try to talk me out of it.

If I want to treat the list of prior jobs of an applicant as a set, and you want to treat it as a list (or maybe even as a stack), neither one of us needs to prove the other one "wrong".

Whether we can collaborate, more than just coexist, remains to be seen. Received on Sun Mar 26 2006 - 20:58:36 CEST

Original text of this message