Re: Table design for application options

> > what do you consider to be a value?
>
> ... I define it as an individual constant. Note that I take things
> like domains, relations, and tuples to be values.

Is a value fundamentally a constant or a thing? What would be examples of non-constants or non-things? Would a person named John be a constant if his age is constantly changing?

> .. my complete disdain for any form of MV database model...

Based on your experience, I can see your viewpoint about MV products. What do you consider to be the is most prominent characteristic of the MV model itself? What is the most significant error or limitation of the MV model itself? Received on Wed Dec 22 2004 - 15:33:34 CST