| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: conditional dropping of columns/constraints |
| Date: | 2009-05-05 15:10:03 |
| Message-ID: | 17130.1241536203@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, May 5, 2009 at 8:56 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> We have debated CREATE ... IF NOT EXISTS in the past, and there is no
>> consensus on what it should do, so we don't have it for any command. That is
>> quite a different case from what's being asked for, and the two should not
>> be conflated.
> I must be missing something, because the semantics of CREATE ... IF
> NOT EXISTS seem pretty well-defined to me,
Please go read the prior threads (I think searching for "CINE" might
help, because we pretty shortly started abbreviating it like that).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2009-05-05 15:11:03 | Re: bytea vs. pg_dump |
| Previous Message | Dave Page | 2009-05-05 15:07:13 | Re: any idea why http://www.postgresql.org/community/survey.61 reverts to old values after a while ? |