[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sapdb-general
Subject:    AW: Stored procedures and Cocoon (jdbc)
From:       "Anhaus, Thomas" <thomas.anhaus () sap ! com>
Date:       2004-09-24 5:31:53
Message-ID: 73DFF891F8024B48AD56B594C4C5038A0FB958 () dewdfe23 ! wdf ! sap ! corp
[Download RAW message or body]

Oscar Picasso wrote :

>
>Hi,
>
>I use MaxDB with Cocoon, the XML/Web Application framework, 
>and came across
>something strange.
>
>If I call a MaxDB a recently modified stored procedure from 
>Cocoon (with jdbc)
>I get the results that would have been returned by the old 
>version of the
>procedure. However the data returned is uptodate. So these 
>results are not
>caused by Cocoon caching the data.
>
>Furthermore if I test the procedure with sqlcli or directly 
>from java I get the
>result corresponding to the new definition.
>
>I seems that the old definition of the procedure is cached 
>somewhere. How can
>this happen ? Is there a mean to force the driver to use the 
>new definition of
>the procedure?
>

This is a known problem. The stored procedure execution plan is cached
in the catalog cache of your session.
You will not see the new version of the stored procedure until you
end your session and open a new one. 
We will change this behavior with version 7.6.

Best Regards,
Thomas

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=sapdb-general@progressive-comp.com

[prev in list] [next in list] [prev in thread] [next in thread]