[
https://issues.apache.org/jira/browse/DERBY-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5578:
---------------------------------
Attachment: derby-5578-upgrade.sql
derby-5578-create.sql
Attaching derby-5578-create.sql and derby-5578-upgrade.sql. These are scripts
which I used to buddy-test this feature. The first script relies on the wrapper
DatabaseMetaData functions attached to DERBY-3973. Here's how you run these
scripts:
o First run derby-5578-create.sql using an earlier release like 10.8.2.2. This
script creates a trigger and registers functions to wrap the DatabaseMetaData
methods.
o Then run derby-5578-upgrade.sql using the 10.10 trunk. This script
hard-upgrades the database, adding the new
SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS procedure.
The scripts verify that SYSCS_INVALIDATE_STORED_STATEMENTS marks all stored
prepared statements as invalid in SYS.SYSSTATEMENTS. The scripts verify that
invoking the trigger after the invalidation causes it to be marked as valid and
updates its lastcompiled timestamp. Those columns in SYS.SYSSTATEMENTS are
similarly updated for a DatabaseMetaData method when you invoke it after the
bulk invalidation.
This indicates to me that SYSCS_INVALIDATE_STORED_STATEMENTS behaves as
described in the Reference Manual.
> 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
>
>
> 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
