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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/03/15 15:24:14 UTC

[jira] [Updated] (DERBY-5578) Provide a way to invalidate stored prepared statements

     [ https://issues.apache.org/jira/browse/DERBY-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-5578:
---------------------------------

    Attachment: releaseNote.html

Adding a release note based on the Reference Manual's description of the procedure.
                
> Provide a way to invalidate stored prepared statements
> ------------------------------------------------------
>
>                 Key: DERBY-5578
>                 URL: https://issues.apache.org/jira/browse/DERBY-5578
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>             Fix For: 10.10.0.0
>
>         Attachments: derby-5578-create.sql, DERBY5578_patch1_diff.txt, DERBY5578_patch2_diff.txt, derby-5578-upgrade.sql, releaseNote.html
>
>
> In various support situations I have seen problems with JDBC metadata stored prepared statements or trigger stored prepared statements that need to be invalidated.  It would be nice to have a way to do this in the field.  For 10.9 a stored procedure would make most sense, but it would be good to have something available in the release branches too.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira