Subject | Re: [firebird-support] Firebird 3: Not able to UPDATE RDB$Procedures |
---|---|
Author | Mark Rotteveel |
Post date | 2018-05-31T20:10:11Z |
On 2018-05-31 17:51, Chuck Belanger phytotech@...
[firebird-support] wrote:
statement used?
As an aside, deleting those sources may make it harder to find out
exactly what the stored procedure etc does, but a determined person can
still reverse engineer it from the BLR. You should ask yourself if you
should go through the trouble of deleting, and why.
Mark
[firebird-support] wrote:
> Hello:What is the full Firebird version used, and exactly what was the
>
> Per googling and Carlos Cantu's FB3 Migration Guide (page: 110), we are
> still allowed to set RDB$PROCEDURE_SOURCE = null, and yet when trying
> to
> do just that on my app's converted FB2.5 to FB3 database, I am getting
> "update not allowed on Systems tables." ISC ERROR CODE 335545030
>
> I noticed a mention that at some point there will be another option to
> blank out this metadata information, but more likely in FB4.
>
> To make this issue more interesting, from within IB_Expert, I can do an
> update of the RDB$Procedures table on one converted DB, but not on the
> working DB. As far as I can tell the tables and DB are essentially the
> same.
>
> Does anyone know what is going on here? Is there another way to blank
> out the Procedure source code?
statement used?
As an aside, deleting those sources may make it harder to find out
exactly what the stored procedure etc does, but a determined person can
still reverse engineer it from the BLR. You should ask yourself if you
should go through the trouble of deleting, and why.
Mark