Helen, >> Martin Agren wrote: >> << >> ... >> 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. > > 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. > > 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.
In 2.5, this isn't the case anymore. http://tracker.firebirdsql.org/browse/CORE-2052 -- With regards, Thomas Steinmaurer * Firebird Foundation Committee Member http://www.firebirdsql.org/en/firebird-foundation/ * Upscene Productions - Database Tools for Developers http://www.upscene.com/ * My Blog http://blog.upscene.com/thomas/index.php
