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] [Commented] (DERBY-5578) Provide a way to invalidate stored prepared statements
Date Thu, 31 May 2012 00:44:23 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286234#comment-13286234
] 

Mamta A. Satoor commented on DERBY-5578:
----------------------------------------

While writing one of the tests for this procedure, I saw that, as a dba, I was able to grant
the execute permission on this procedure to another user.
grant execute on procedure syscs_util.SYSCS_INVALIDATE_STORED_STATEMENTS to sam;

But a similar grant on sysibm.sqlprocedures by dbo to another user fails
grant execute on procedure sysibm.sqlprocedures to sam;
ERROR 42509: Specified grant or revoke operation is not allowed on object 'SYSIBM.SQLPROCEDURES'.

Looking at the code, I found that SchemaDescriptor.isSchemaWithGrantableRoutines() identifies
SQLJ and SYSCS_UTIL as schemas which allows grant on it's routines. And that is why we were
able to grant execute on syscs_util.SYSCS_INVALIDATE_STORED_STATEMENTS but not on sysibm.sqlprocedures.

So, the question is should the new procedure for invalidating stored statements have grantable
execute permission? If not, then should we move it to some other schema like sysibm which
does not allow grant execute permission on it's procedures?
                
> 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

        

Mime
View raw message