>> Because the bulk insert command would bypass triggers, which is
>> something you don't want to allow everybody.
>>
>>
> That's true, but isn't that a general problem and not particularly
> specific to bulk insert.

Sorry, I cannot trace your ideas here, please elaborate.

> 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.

We could, but how do we prevent Joe from adding a
isc_dpb_ignore_triggers to DPB and bypass the audit log triggers, and
allow Ann doing this for bulk load stuff?

> 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.

Not sure that I want to merge those permissions... but you're right - a
guy that has DROP permission on trigger does not need BULK INSERT
permission to disable trigger.

Roman