| Subject | Re: [firebird-support] Re: DDL updates in 2.5 |
|---|---|
| Author | Helen Borrie |
| Post date | 2011-11-21T22:19:46Z |
At 08:12 AM 22/11/2011, Aage Johansen wrote:
On Classic and Superclassic, each connection has its own cache. If Martin was doing his testing in that environment, his FR client would still be working with the old BLR, while new connections would work with the new BLR.
./heLen
>Martin Agren wrote:No, Aage, you're not mistaken. The compiled BLR goes into the cache and stays there for re-use until the database is left with no further connections (or is shut down purposely). Superserver's cache is shared between all connections so the Flamerobin client will still execute the old BLR.
><<
>...
>Data output from my stored proc isnt reflecting the changes I have
>made. I make changes in DDL, check the "new" dataset (Flamerobin or
>my client app) and am not getting the desired results as data is
>unchanged. I make another change, still no effect. Then, when
>disconnectiong and restarting my client side apps all the changes
>suddenly appear.
> >>
>
>Will your stored procedure need re-compiling before changes will show
>up in the results? I don't think the SP is recompiled until the
>database is closed and reopened - it could be difficult to recompile
>for you and keeping the old one for other users. OTOH - I could be mistaken.
On Classic and Superclassic, each connection has its own cache. If Martin was doing his testing in that environment, his FR client would still be working with the old BLR, while new connections would work with the new BLR.
./heLen