| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: Lucid statement of the MV vs RM position?
JOG wrote:
> Jon Heggland wrote: >
>
>
> These are great examples Jon. GUNF is perhaps a missing piece in my
> theoretical understanding as it seems to state formally what I have
> been struggling with intuitively for months, when I've commented that
> "sets shouldn't just pop into existence from nowhere". I have been
> struggling with an example for a while:
>
> A fish can be gold.
> A cow can be brown.
> A cow can be black and white.
>
> Animal | Colour
> -----------------
> Fish { Gold }
> Cow { Brown }
> Cow { Black, White }
>
> With the PK { Animal, Colour }. If I Ungroup I will generate:
>
> Animal | Colour
> -----------------
> Fish Gold
> Cow Brown
> Cow Black
> Cow White
>
> But this is now not in GUNF because if I regroup I'll get:
>
> Animal | Colour
> -----------------
> Fish { Gold }
> Cow { Brown, Black, White }
>
> Which is of course nonsense in reference to my original predicate. Now
> if my understanding is correct, to model this albeit very rough
> information, I can now formally show that I will require an RVA. (I
> could use a surrogate but I would rather not materialize artificial new
> data just to accomodate what I have.)
>
> Someone affirm this to me or shoot my naivite down in flames.
>
I think that an all-key
relation { animal string, colour relation { colour string } }
is very different from
relation { animal string, colour string }
This, of course, maybe exactly why D+D suggest that base relations consisting of other than scalar types are of limited usefulness.
With TutD, I have GROUPed and UNGROUPed a handful of such things, but a key component was never part of the mix. I think you've both uncovered examples which may provide useful insight; thanks.
I'm going to ponder a bit...
> >
![]() |
![]() |