From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: operator exclusion constraints |
Date: | 2009-11-02 11:53:49 |
Message-ID: | 1257162829.28888.11.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 2009-11-01 at 18:07 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > The syntax be easier to read if it was stated as a comparison
> > e.g. in the circle example
> > CHECK ( NOT (NEW.c && c)) USING GIST
>
> I don't think this is a good idea at all. NEW is a nonstandard
> Postgres-ism, and introducing it into this syntax doesn't seem very
> future-proof to me. What's more, the above is not in the least
> analogous to a regular CHECK constraint, because there's some implicit
> notion of "c" ranging over all other rows, which is not what is meant
> by the same column reference in a CHECK constraint.
>
> I agree that the proposed syntax is a bit awkward, but this isn't
> better.
Agreed. Just looking for readable, future-proof syntax.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-11-02 14:11:59 | Re: Architecture of walreceiver (Streaming Replication) |
Previous Message | Devrim GÜNDÜZ | 2009-11-02 11:10:26 | Re: alpha2 bundled -- please verify |