Subject | Re: [ib-support] Re: Metadata security |
---|---|
Author | Martijn Tonies |
Post date | 2002-07-25T07:40:49Z |
Hi,
Don't know if this bug was fixed -- but having a source of NULL
would cause triggers to be executed twice.
So instead of doing NULL, it might be better to do:
UPDATE RDB$TRIGGERS SET RDB$TRIGGER_SOURCE = 'rubbish'
Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
Don't know if this bug was fixed -- but having a source of NULL
would cause triggers to be executed twice.
So instead of doing NULL, it might be better to do:
UPDATE RDB$TRIGGERS SET RDB$TRIGGER_SOURCE = 'rubbish'
Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
> IB6.5 has enhanced metadata security. Not sure about how 'secure'
> this is, since in the specs they mention only that the new
> feature 'protects the data from modification by unauthorized users'.
> I presume this means it is hidden.
>
> FB has very limited metadata security. The only way to keep anyone
> from examining DDL, and only for triggers and procedures, is:
>
> UPDATE RDB$TRIGGERS SET RDB$TRIGGER_SOURCE = NULL
>
> UPDATE RDB$PROCEDURES SET RDB$PROCEDURE_SOURCE = NULL
>
> Ensure you have backup copies of your DDL prior to erasing the source
> in the db. Also, there may be system triggers and procedure source
> that you should not delete! So be selective going about it.
>