BUG#20492: Subsequent calls to stored procedure yield incorrect result
if join is used For procedures with selects that use complicated joins with ON expression re-execution could erroneously ignore this ON expression, giving incorrect result. The problem was that optimized ON expression wasn't saved for re-execution. The solution is to properly save it.
Showing
Please register or sign in to comment