You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2012/07/13 21:42:34 UTC
[jira] [Resolved] (DERBY-5793) Document new
SYSCS_INVALIDATE_STORED_STATEMENTS procedure
[ https://issues.apache.org/jira/browse/DERBY-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-5793.
------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
Issue & fix info: (was: Patch Available)
Thanks very much, Mamta.
Committed patch DERBY-5793.diff to documentation trunk at revision 1361347.
> Document new SYSCS_INVALIDATE_STORED_STATEMENTS procedure
> ---------------------------------------------------------
>
> Key: DERBY-5793
> URL: https://issues.apache.org/jira/browse/DERBY-5793
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Mamta A. Satoor
> Assignee: Kim Haase
> Fix For: 10.10.0.0
>
> Attachments: DERBY-5793.diff, DERBY-5793.stat, rrefsyscsinvalidatestoredstmts.html
>
>
> We should document the procedure that will get added as part of DERBY-5578. The new procedure will invalidate all the stored prepared statements. When such an invalid stored prepared statement is executed next time, it will get recompiled at that point thus generating a new plan for it. This can be a very useful tool from support point of view, especially after upgrades.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira