db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (DERBY-5350) Devguide needs update for definer's rights
Date Mon, 25 Jul 2011 14:55:09 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dag H. Wanvik reassigned DERBY-5350:
------------------------------------

    Assignee: Dag H. Wanvik

> Devguide needs update for definer's rights
> ------------------------------------------
>
>                 Key: DERBY-5350
>                 URL: https://issues.apache.org/jira/browse/DERBY-5350
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.8.1.2
>            Reporter: Knut Anders Hatlen
>            Assignee: Dag H. Wanvik
>         Attachments: cdevcsecureroles.html, derby-5330a.diff
>
>
> I found the following in the Using SQL roles topic of the devguide:
> "Within stored procedures and functions that contain SQL, the current role is on the
authorization stack. Initially, inside a nested connection, the current role is set to that
of the calling context."
> http://db.apache.org/derby/docs/10.8/devguide/cdevcsecureroles.html
> I think this is only correct for procedures running with invoker's rights. For procedures
running with definer's rights, no role is set initially, according to the CREATE PROCEDURE
statement topic in the reference manual:
> "When the procedure is first invoked, no role is set; even if the invoker has set a current
role, the procedure running with definer's rights has no current role set initially."
> http://db.apache.org/derby/docs/10.8/ref/rrefcreateprocedurestatement.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message