Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Vector type (Re: challenging constraint situation -


  • 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: Fri, 26 May 2006 17:59:46 +0200
  • Message-id: <447725F2(dot)5040008(at)magproductions(dot)nl>

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 //



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group