| From: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CREATE OR REPLACE TRIGGER not supported? |
| Date: | 2004-09-13 07:57:44 |
| Message-ID: | 414552F8.8080409@nttdata.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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 <chriskl(at)familyhealth(dot)com(dot)au> 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 <nagayasus(at)nttdata(dot)co(dot)jp>
OpenSource Development Center,
NTT DATA Corp. http://www.nttdata.co.jp/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2004-09-13 08:21:43 | Re: pgxs default installation + various fixes |
| Previous Message | Daniel Schuchardt | 2004-09-13 07:37:14 | Re: beta1 & beta2 & Windows & heavy load |