Subject Stored Procedure Caching in FB 2
Author Guido Klapperich
In the past with Firebird 1.5 I have done developing stored procedures
quite often like this:
- connect with my client app to the database
- change and compile the sp
- run the sp from the client, check the results and commit transaction

As I said, this worked fine with FB 1.5.
Now I have switched to FB 2.01 and I always have to reconnect to the
database with my client app to see the changes to the sp, after I have
compiled it. When I switch back to FB 1.5, all works fine again.

Now my question: Has FB 2 some kind of caching, so that my client has to
reconnect to see the changes done to the sp?