Subject | Re: [Firebird-Architect] Bulk loader. |
---|---|
Author | Jim Starkey |
Post date | 2007-11-04T21:01:17Z |
Roman Rokytskyy wrote:
specific to bulk insert.
But while we're one the subject, wouldn't it be nice to be able disable
triggers on a per-connection basis? Very easy to do and would be use in
this case as well as many others.
Even better, wouldn't it be to be able to disable classes of triggers,
again on a per-connection basis? A trigger could have declare trigger
classes it was a member of.
Oh, you don't need a privilege to disable triggers if you restrict it to
people with the right to drop the trigger. Kinda the same thing, really.
>>> Hmmm... personally I would go with GRANT BULK INSERT ON <...> TO <...> .That's true, but isn't that a general problem and not particularly
>>>
>>>
>>>
>> Why yet another permission? Why not just check for each of the
>> individual rights required to do the job?
>>
>
> Because the bulk insert command would bypass triggers, which is
> something you don't want to allow everybody.
>
>
specific to bulk insert.
But while we're one the subject, wouldn't it be nice to be able disable
triggers on a per-connection basis? Very easy to do and would be use in
this case as well as many others.
Even better, wouldn't it be to be able to disable classes of triggers,
again on a per-connection basis? A trigger could have declare trigger
classes it was a member of.
Oh, you don't need a privilege to disable triggers if you restrict it to
people with the right to drop the trigger. Kinda the same thing, really.