Frank Schimmelpfennig wrote : >Hello, >I faced an interesting effect when replacing a dbproc with a >newer version: >(1) I was executing the old version of the dbproc in question with a >non-owner user. >(2) I droped and re-created the new version of the dbproc with >the dbproc's >owner user while the non-owner user still had his db session from (1). >(3) Then I was executing again the dbproc with the non-owner user. - It >seemed that the old version of the dbproc was executed. >Is this the case? Is the (parsed) code of a dbproc cached for an user >session (non-owner) even if this dbproc is droped and exchanged >(=re-created) by another version? What have I to do to enforce >non-users to >execute the new version of the dbproc (e.g. re-connect to the >database)? > >Thanks in advance! >kind regards >Frank > > >-- >MaxDB Discussion Mailing List >For list archives: http://lists.mysql.com/maxdb >To unsubscribe: >http://lists.mysql.com/maxdb?>[EMAIL PROTECTED] > >
This is a known problem of the current dbproc implementation. We hopefully will solve it very soon. You have to end your session and to reconnect to force the new version to be executed. Best Regards, Thomas -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
