Subject | dependent sps & triggers need recompilation |
---|---|
Author | woodsmailbox |
Post date | 2009-02-26T18:36:35Z |
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) ?
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) ?