[
https://issues.apache.org/jira/browse/DERBY-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-5578:
-----------------------------------
Issue & fix info: High Value Fix,Newcomer,Release Note Needed (was: High
Value Fix,Newcomer)
> 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
