| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: operator exclusion constraints |
| Date: | 2009-11-06 19:11:28 |
| Message-ID: | 1257534688.28470.215.camel@monkey-cat.sm.truviso.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2009-11-06 at 10:50 -0800, David E. Wheeler wrote:
> Is your objection to EXCLUDE for cases when there is no USING clause?
>
> EXLUDE (room, during) BY (=, &&)
>
"Objection" is too strong a word. EXCLUDE is a transitive verb, so it's
slightly confusing in the above case.
> BTW, is it the case that room maps to = and during maps to && in this
> example? If so, wouldn't it make more sense to combine them?
>
> EXCLUSION (room WITH =, during WITH &&)
That's (close to) the current syntax, which I'm perfectly fine with.
Form 1 with EXCLUSION/CHECK WITH is the current syntax.
It seemed like the winds were shifting towards separating them, but I'm
happy leaving it alone.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2009-11-06 19:13:53 | Re: operator exclusion constraints |
| Previous Message | Andrew Dunstan | 2009-11-06 19:10:27 | Re: plperl and inline functions -- first draft |