From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: operator exclusion constraints |
Date: | 2009-11-23 07:20:24 |
Message-ID: | 1258960824.23718.3.camel@fsopti579.F-Secure.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On sön, 2009-11-22 at 16:03 -0800, David Fetter wrote:
> What, if anything, does the standard have to say about violations of
> ASSERTIONs? I know these aren't ASSERTIONs, but they much more
> closely resemble them than they do UNIQUE constraints.
An assertion is by definition a constraint that is a schema component
independent of a table. Which an exclusion constraint may or may not
be, but it's an independent issue. (To clarify: It currently can't be,
because assertions are not implemented, but when they are, it could be.)
For the same reason, assertions don't have separate error codes, because
they are just constraints after all.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-11-23 08:26:18 | Re: Unicode UTF-8 table formatting for psql text output |
Previous Message | Andrew Dunstan | 2009-11-23 05:58:18 | Re: [COMMITTERS] pgsql: Remove -w (--ignore-all-space) option from pg_regress's diff |