From: | Alban Hertroys <alban(at)magproductions(dot)nl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Vector type (Re: challenging constraint situation - |
Date: | 2006-05-26 15:59:46 |
Message-ID: | 447725F2.5040008@magproductions.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Alban Hertroys <alban(at)magproductions(dot)nl> writes:
>
>>I'd say "unique constraint violation" right here (provided there's a
>>unique constraint on this column, of course). The order in which these
>>are inserted/updated doesn't seem to matter either. I'm afraid I'm still
>>missing the point...
>
> The point is that btree depends on a number of assumptions about the
> behavior of the operators in an operator class, and one of those
> assumptions is that "equality" is transitive.
So, referring back to your example you mean that though B overlaps A,
and C overlaps B, C doesn't overlap A and thus they're not transitive.
I see.
--
Alban Hertroys
alban(at)magproductions(dot)nl
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-05-26 16:00:02 | Re: LDAP authentication |
Previous Message | Rafal Pietrak | 2006-05-26 15:58:32 | Re: Restricting access to rows? |