> And how often do you need to redefine a trigger (as opposed to its
> underlying function), anyway?

I just want to know why not supported.
It's not a serious problem.

Tom Lane wrote:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> 
>>>Is threre any reason not to support "CREATE OR REPLACE"
>>>only for triggers?
> 
> 
>>Because the oid of a trigger doesn't matter.  You can go being; drop 
>>trigger; create trigger; commit; atomically.
> 
> 
> And how often do you need to redefine a trigger (as opposed to its
> underlying function), anyway?
> 
> Sure, given infinite manpower we would support this.  But it seems very
> far down the to-do list to me.
> 
>                       regards, tom lane
> 


-- 
NAGAYASU Satoshi <[EMAIL PROTECTED]>
OpenSource Development Center,
NTT DATA Corp. http://www.nttdata.co.jp/

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org

Reply via email to