db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5578) Provide a way to invalidate stored prepared statements
Date Wed, 30 May 2012 16:55:23 GMT

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

Mamta A. Satoor updated DERBY-5578:

    Attachment: DERBY5578_patch1_diff.txt

Attaching a patch which adds the new stored procedure which will invalidate all the stored
statements. Next execution of the statement will cause it to recompile. I will work next on
adding regression tests and upgrade tests.
> 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
>         Attachments: DERBY5578_patch1_diff.txt
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message