db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5578) Provide a way to invalidate stored prepared statements
Date Fri, 26 Oct 2012 15:37:12 GMT

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

Rick Hillegas commented on DERBY-5578:

The following script demonstrates what the Reference Manual says:


o However, the DBO can grant other users the privilege to run this procedure.

connect 'jdbc:derby:memory:db;create=true;user=test_dbo';

-- turn on NATIVE authentication. won't take effect until you bounce the database.
call syscs_util.syscs_create_user( 'test_dbo', 'test_dbopassword' );
call syscs_util.syscs_create_user( 'fred', 'fredpassword' );

-- bounce the database in order to turn on NATIVE authentication
connect 'jdbc:derby:memory:db;shutdown=true';
connect 'jdbc:derby:memory:db;user=test_dbo;password=test_dbopassword' as dbo;

-- the DBO can run this procedure
call syscs_util.syscs_invalidate_stored_statements();

connect 'jdbc:derby:memory:db;user=fred;password=fredpassword' as fred;

-- should fail because privilege has not been granted
call syscs_util.syscs_invalidate_stored_statements();

set connection dbo;

--grant privilege to fred;
grant execute on procedure syscs_util.syscs_invalidate_stored_statements to fred;

set connection fred;

-- should work now that fred has been granted privilege
call syscs_util.syscs_invalidate_stored_statements();

> 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:
>         Attachments: derby-5578-create.sql, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message