Skip site navigation (1) Skip section navigation (2)

Re: drop if exists remainder

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: drop if exists remainder
Date: 2006-02-05 16:15:42
Message-ID: 43E624AE.702@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches

Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>  
>
>>Here's a first draft patch for DROP ... IF EXISTS for the remaining 
>>cases, namely: LANGUAGE, TABLESPACE, TRIGGER OPERATOR CLASS, FUNCTION, 
>>AGGREGATE, OPERATOR, CAST and RULE.
>>    
>>
>
>At what point does this stop being useful and become mere bloat?
>The only case I can ever recall being actually asked for was the
>TABLE case ...
>
>
>  
>

Chris KL said it should be done for all on the grounds of consistency. 
But I will happily stop right now if that's not the general view - I'm 
only doing this to complete something I started.

cheers

andrew


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-02-05 16:16:39
Subject: Re: Shared memory and memory context question
Previous:From: Tom LaneDate: 2006-02-05 16:02:47
Subject: Re: drop if exists remainder

pgsql-patches by date

Next:From: Joachim WielandDate: 2006-02-05 17:24:04
Subject: Re: TODO-Item: TRUNCATE ... CASCADE
Previous:From: Tom LaneDate: 2006-02-05 16:02:47
Subject: Re: drop if exists remainder

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group