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 Fri, 01 Jun 2012 20:14: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_patch2_diff.txt

Attaching patch DERBY5578_patch2_diff.txt which is ready for commit. This patch has required
code changes to add a new procedure which will allow users to invalidate all the stored statements
inside SYS.SYSSTATEMENTS. At this point, there are two types of stored statements in that
system table - statements for metadata calls and statements for trigger action plans. I have
also added test cases including the regression tests and upgrade tests. Upgrade tests show
that this procedure is available only after hard upgrade. Regression test show how the procedure
can be executed only by dba unless dba grants execute permission to other users. Additionally,
it has test cases showing statements getting invalidated by the procedure call and subsequent
execution of metadata call or trigger causing their corresponding statements to become valid.

Please let me know if there is any feedback on the code changes or any other test cases I
should add. 

The changes for this jira can only go in as part of a major release since it fiddles around
wit system tables. This jira can't be backported to released branches.

If Rick sees a need to cut another 10.9 release jars, we can backport it to 10.9 but otherwise
it will need to go into next major release. 

                
> 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, DERBY5578_patch2_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

        

Mime
View raw message