Re: Table design for application options

From: Neo <neo55592_at_hotmail.com>
Date: 4 Jan 2005 07:50:49 -0800
Message-ID: <1104853849.067487.81260_at_c13g2000cwb.googlegroups.com>


> As far as a value goes, I define it as an individual constant. Note
> that I take things like domains, relations, and tuples to be values.
> ... value = individual constant

So a value is a constant and examples of constants are domains, relations and tuples. Is this correct?

> The MV data model is fatally flawed, just like hierarchal.

I would agree that RM's scope is broader than that of MV and hierarchal. While a model's flaws makes is "fatal" for some scope of applications, doesn't it make it more efficient for some limited cases? Do you know of a data model without flaws? Which one? What exactly is a "fatal flaw" with respect to data models? Received on Tue Jan 04 2005 - 16:50:49 CET

Original text of this message