Hi,

> There are a few cases where the whole chain of dependent sps &
> triggers need recompilation whenever a certain sp changes. For
> instance, today I had a sp which's execution got a "multiple rows in
> singleton" error. After fixing it, all its callers (sps & triggers
> alike) kept insisting on executing the old version of the procedure.
> Only executing the sp directly worked. I use 2.1.2.
>
> I'm sure it happen this before, but didn't had time to investigate. I
> just got used to recompiling everything.
>
> So the question is, is this a known bug or should I try and make up a
> more detailed report (eg. with a db attached, or sumth) ?

Once the BLR version of a routine is loaded, it's cached. You
can unload it either by an explicit recompile (although that
sometimes won't work with multiple connections), or disconnecting
everyone.

With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!

Database questions? Check the forum:
http://www.databasedevelopmentforum.com