[
https://issues.apache.org/jira/browse/DERBY-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286383#comment-13286383
]
Knut Anders Hatlen commented on DERBY-5578:
-------------------------------------------
I don't see any reason why we'd want to deny the DBO's granting the execute
permission on this procedure, so +1 to keeping it in SYSCS_UTIL.
I think you're right that only meta-data queries and triggers are stored in
SYSSTATEMENTS. It looks like there used to be syntax for CREATE STATEMENT,
which allowed user-defined queries to be stored there too, but that syntax is
disabled now.
> 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
