Re: alter enum add value if not exists

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: alter enum add value if not exists
Date: 2012-09-22 21:49:19
Message-ID: 505E325F.70907@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 09/22/2012 05:39 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> The enum piece is now committed.
> BTW, looking at that a second time ... the other CREATE IF NOT EXISTS
> options we have issue a NOTICE when skipping the CREATE action. Is
> there a reason this shouldn't do the same?
>
>

Not really, I guess we should for the sake of consistency, although TBH
I find it just useless noise and rather wish we hadn't started the trend
when we did the first DROP IF NOT EXISTS stuff.

I'll add it.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2012-09-22 21:55:37 Re: alter enum add value if not exists
Previous Message Tom Lane 2012-09-22 21:39:28 Re: alter enum add value if not exists