| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: SQL, related records (quotes)
Dan Guntermann wrote:
> "Stefan Rybacki" <stefan.rybacki_at_gmx.net> wrote in message
> news:3i78t2Fk4c3tU1_at_individual.net...
>
>>Dan Guntermann wrote: >> >>>... >>>But alas, not many implementations allow for assertions of antisymmetry, >>>though it could be done with a trigger. This approach would enforce the >>>condition that >>>for all (child, parent) relationships that are members of hierarchies, >>>there does not exist a tuple of (parent, child). It also has the >>>limiting factor of disallowing single node hierarchies. >> >>You meant non-symmetry since anti-symmetry says: you can have (child, >>parent) and (parent, child) at the same time execept parent=child
anti-symmetry + non-reflexifity = non-symmetry
Since anti-symmetry disallow symmetry except if both relation partners are equal. And non-reflexifity disallow this case a R a, so what remains is non-symmetry.
>
> child parent
> 6 3
> 3 6
>
> If it doesn't, then it makes sense that the DBMS reject such a condition.
> Obviously 6 does not equal 3.
Correct.
>
>
>>Just mentioned ;) (I know antisymmetry works here since you said you don't >>allow reflexive tupels)
I know
>
> However, we have a constraint that asserts the condition a <> b. Thus, ~(a
> R b ^ b R a) V FALSE reduces to:
> ~(a R b ^ b R a).
Correct, this is exactly non-symmetry.
>
>
>>Regards >>Stefan >> >> >>>...
Regards
Stefan
>
>
Received on Sun Jun 26 2005 - 10:36:18 CDT
![]() |
![]() |