| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: RA with MV attributes
David wrote:
> paul c wrote:
>
>>David wrote: >> >> >>>... >>>Why can't we say that *by definition* the set of attributes of a >>>relation is part of its state not its type? >>>... >> >>We can say anything we want "by definition", the question is where does >>saying it get us? What conclusions does it lead to and so forth.
>>I >>like your suggestions because they seem to have something behind them, >>but don't ask me what, exactly. I wish you would distinguish whether >>you are talking about physical implementations or user concepts.
That's a bit too blurry for me. What is simple as compared to what is too simple depends very much on the objective, as I think somebody said "as simple as possible, but no simpler!".
I do think that once one has a definition it is important to proceed to positioning it in the scheme of things, for example is this a physical approach for storing two relations in one or is it an attempt to promote three-valued logic or is it something else? I find this thread interesting because I think rva's have not been explored very thoroughly (perhaps they should be discounted eventually, but I don't think anybody has yet made a good case, or at least one I could understand, for this, yet).
The "advantage" of avoiding redundancy in general is also a blurred one for me. If the domain we're interested in is what cars certain people own, I don't find it all redundant that two people may happen to own the same kind of car. Whereas avoiding physical redundancy as far as computer machinery is concerned is a very worthy goal.
p Received on Wed Jan 17 2007 - 08:58:11 CST
![]() |
![]() |