From: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |
Date: | 2005-07-01 07:31:03 |
Message-ID: | 42C4F137.6000507@nttdata.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> The table owner can drop and create triggers - so why shouldn't they be
> able to enable and disable them?
For convenience or easy operation.
I believe the user doesn't like to create same triggers again and again.
Christopher Kings-Lynne wrote:
>>>ALTER TABLE <table> ENABLE TRIGGER <trigname>
>>>ALTER TABLE <table> DISABLE TRIGGER <trigname>
>>
>>
>>Bruce said to allow them only super-user,
>>but currently this patch allows also the table owner.
>
>
> The table owner can drop and create triggers - so why shouldn't they be
> able to enable and disable them?
>
> Chris
>
>
--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2005-07-01 07:44:00 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |
Previous Message | Christopher Kings-Lynne | 2005-07-01 07:29:23 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2005-07-01 07:44:00 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |
Previous Message | Christopher Kings-Lynne | 2005-07-01 07:29:23 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |