Subject | Re: [firebird-support] ROLES and USERS |
---|---|
Author | Helen Borrie |
Post date | 2008-02-28T03:09:01Z |
At 12:56 PM 28/02/2008, you wrote:
Anyone can read metadata.
Anyone can create new objects in a database.
Only the Owner of an object can alter that object. (The Owner is the user that created the object.)
A trigger belongs to a table, so only the Owner of that table may create or alter triggers for that table.
The Owner of a database, or SYSDBA, can drop a database.
The Owner of a table can delete the source for a trigger. That makes the source invisible. Likewise, the owner of a SP can delete the source for the SP. Deleting the source doesn't affect how the trigger or SP behaves but, of course, if the owner wants to drop or alter the body of that trigger or SP, s/he had better have a copy of the source archived safely somewhere.
Note, the Owner can do
ALTER TRIGGER aTrigger INACTIVE (or ACTIVE)
without affecting the compiled code of the trigger.
./heLen
>Hi all,ROLEs won't do that. They are packages of SQL permissions regarding access to *data*. Access to the metadata definitions is determined by ownership, not by SQL permissions.
>
>How to make the ROLES in FB (1.5) so I could manage the USERS, I mean
>I need to manage some users therefore not everyone of them can
>open/alter the script of SP, Trigger and Table Structure I have made.
Anyone can read metadata.
Anyone can create new objects in a database.
Only the Owner of an object can alter that object. (The Owner is the user that created the object.)
A trigger belongs to a table, so only the Owner of that table may create or alter triggers for that table.
The Owner of a database, or SYSDBA, can drop a database.
The Owner of a table can delete the source for a trigger. That makes the source invisible. Likewise, the owner of a SP can delete the source for the SP. Deleting the source doesn't affect how the trigger or SP behaves but, of course, if the owner wants to drop or alter the body of that trigger or SP, s/he had better have a copy of the source archived safely somewhere.
Note, the Owner can do
ALTER TRIGGER aTrigger INACTIVE (or ACTIVE)
without affecting the compiled code of the trigger.
./heLen