| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | David Christensen <david(at)endpoint(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Add missing keywords to gram.y's unreserved_keywords list. |
| Date: | 2011-03-11 19:59:46 |
| Message-ID: | 26046.1299873586@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 03/11/2011 02:50 PM, David Christensen wrote:
>> On Mar 11, 2011, at 1:40 PM, Robert Haas wrote:
>>> ALTER CONSTRAINT ... VALID sounds like it just marks the constraint as
>>> valid. "VALIDATE CONSTRAINT" sounds like it scans and checks that the
>>> constraint is valid.
> SET VALID? (c.f. SET NULL).
That sounds the best so far, but maybe we should think about other
phrases altogether (ie, not arising from the word "valid")? I don't
have any great ideas offhand, just trying to think outside the box.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-03-11 20:00:32 | Re: Re: [COMMITTERS] pgsql: Add missing keywords to gram.y's unreserved_keywords list. |
| Previous Message | Andrew Dunstan | 2011-03-11 19:56:13 | Re: Re: [COMMITTERS] pgsql: Add missing keywords to gram.y's unreserved_keywords list. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-03-11 20:00:32 | Re: Re: [COMMITTERS] pgsql: Add missing keywords to gram.y's unreserved_keywords list. |
| Previous Message | Andrew Dunstan | 2011-03-11 19:56:13 | Re: Re: [COMMITTERS] pgsql: Add missing keywords to gram.y's unreserved_keywords list. |