Subject | Re: [firebird-support] Why do I recompile all the stored procedure after drop a irrelevant field? |
---|---|
Author | Helen Borrie |
Post date | 2011-10-15T22:53:29Z |
At 11:13 AM 16/10/2011, william_yuwei wrote:
./hb
>HI, AllThe "compiled" BLR, which includes the metadata of objects involved, is stored persistently at the time the module is [re]created. It even survives backup and restore. It does not magically recompile itself when you alter the structure of tables that are operated on by the module. However, I seem to recall a bug that allowed you to drop a column or domain that had dependencies in BLR. Check the PSQL bug fixes in the v.2.1.4 release notes.
>
>Using Firebird 2.1.3, I have a table, called, Order, which have a not null field POSTED with default source 'N'. Later, I removed this field, but all my stored procedures that having UPDATE ORDER SET ...., need to be recomple again, even though there is NO POSTED field involved in the UPDATE statements. If I won't re-compile these stored procedures, I will get '.... column 'unknown', values *** null*** ....' error.
./hb