| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: Generalised approach to storing address details
JOG wrote:
> vc wrote:
> > JOG wrote:
> [snips]
> > >
> > > This currently is unclear to me - an ancestor relation is a relation
> > > like any other, and can be enumerated like any other. Take a domain D =
> > > {grandfather, father, son}. The ancestor relation would be A = {
> > > (Grandfather, father), (Grandfather, son), (father, son) }. What is so
> > > inexpressible there? Given that the above is no doubt obvious to you,
> > > if you have the inclination, perhaps you clarify/expand what you mean
> > > by "the ancestor relation cannot be expressed in f.o.l. and r.a".
> >
> > Consider any set of which the ancestor relation is a subset. Any such
> > set is also an "ancestor" relation because it satisfies your
> > definitions. How would you pick up the correct one using only the
> > first-order logic language ?
> >
>
>
F.o.l. does not allow circular definitions: P(x, y) =def. ...P(..) would be ill-forme -- P cannot appear on the right.
>
Prolog allows circular definitions because Prolog is an extension of a specific fragment of f.o.l. and can handle such definitions with its SLD engine, but not very well, for example your older definition, although "theoretically" correct, will lead to an infinite recursion.
>Now the RM is not an inference
There are equivalents e.g. Oracle's "connect by" or Date's transitive closure operator.
>equivalent via a RDBMS by setting up a
I do not understand what you suggest. Received on Fri Dec 15 2006 - 15:26:34 CST
![]() |
![]() |