Subject | Re: [firebird-support] Can I Activate/Inactivate a trigger from a non -SYSDBA account ? |
---|---|
Author | Helen Borrie |
Post date | 2003-06-23T05:42:50Z |
At 10:16 PM 22/06/2003 -0700, you wrote:
owner can modify an object's metadata, for obvious reasons. What would
happen to data integrity if any old user could disable triggers?
environment where clients are logged in to the database in their own
right. It could be done in an n-tier architecture, where you had a server
application running with owner or sysdba rights which acted as a traffic
cop/benevolent dictator/proxy for the clients and could lock out all but
the requesting user for the period that the trigger was inactive.
I'm curious to know what requirement makes you need to give users the
ability to disable triggers...
heLen
>Hi,These are data privileges
>
>I'm traing to inactivate a trigger from a normal user
>account(non-SYSDBA).
>with:
>
>ALTER trigger AI_MYTABLE_IDMYTABLE inactive;
>
>And I receive an error message...
>
>MODIFY TRIGGER failed.
>no permission for control access to TABLE MYTABLE.
>
>My user has all rights(INSERT,UPDATE,DELETE,REFERENCE)
>on table MYTABLE and work fine in all situations
>but in this particular case not.Ordinary users don't get metadata privileges. Only sysdba or the object
owner can modify an object's metadata, for obvious reasons. What would
happen to data integrity if any old user could disable triggers?
>It's not a practicable thing to try to do in a multi-user client/server
>Can someone help me?
environment where clients are logged in to the database in their own
right. It could be done in an n-tier architecture, where you had a server
application running with owner or sysdba rights which acted as a traffic
cop/benevolent dictator/proxy for the clients and could lock out all but
the requesting user for the period that the trigger was inactive.
I'm curious to know what requirement makes you need to give users the
ability to disable triggers...
heLen