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:52:13 |
Message-ID: | 42C4F62D.9050002@nttdata.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> I said why _shouldn't_. I was agreeing with you.
Oops. Sorry.
I don't know why only super-user shold be able to enable/disable tirggers.
I believe the table owner want to enable/disable triggers,
because I always need it.
Loading huge data set into the table with triggers(or fk) is very painful.
Christopher Kings-Lynne wrote:
>
> Satoshi Nagayasu wrote:
>
>>>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.
>
>
> I said why _shouldn't_. I was agreeing with you.
>
> Chris
>
>
--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2005-07-01 08:05:22 | Re: [PATCHES] Users/Groups -> Roles |
Previous Message | Christopher Kings-Lynne | 2005-07-01 07:44:00 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2005-07-01 08:05:22 | Re: [PATCHES] Users/Groups -> Roles |
Previous Message | Christopher Kings-Lynne | 2005-07-01 07:44:00 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |