[
https://issues.apache.org/jira/browse/DERBY-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563603#action_12563603
]
Daniel John Debrunner commented on DERBY-2207:
----------------------------------------------
The SQL TECHNICAL CORRIGENDUM 1 section 18.3 changes the syntax rules for SET
ROLE. My reading of it is that NONE can now only appear as a keyword, NONE as a
value expression does not mean set the current role to nothing. Not sure what
the code is doing at the moment, I couldn't see any processing for NONE.
For connection pooling I think that the reset of a connection from Derby's
PooledConnection needs to reset the role to nothing. Is that being handled?
> Improve usability of Derby's client/server security by implementing ANSI Roles
> ------------------------------------------------------------------------------
>
> Key: DERBY-2207
> URL: https://issues.apache.org/jira/browse/DERBY-2207
> Project: Derby
> Issue Type: New Feature
> Components: Security, SQL
> Reporter: Rick Hillegas
> Assignee: Dag H. Wanvik
> Attachments: spec.html, spec.html, spec.html, spec.html, spec.html,
> spec.html
>
>
> Implementing ANSI Roles will make it easier to manage security for multi-user
> applications with high user turnover.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
