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] Commented: (DERBY-3137) SQL roles: add catalog support
Date Tue, 06 Nov 2007 15:56:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540465

Dag H. Wanvik commented on DERBY-3137:

Thanks for the comments, Rick!

1) Thanks for catching that!

2, 3) I think this is a reasonable thing to do. I didn't do it at
first because I wasn't able to read this possibility as legal from the
wording of the standard: Setting a Java null amounts to a SQL NULL on
the SQL level (JDBC 4.0, §, p 102), and SQL §18.3 doesn't seem
to allow for NULL, cf. for example GR 3.

Still, I think it is a reasonable thing to do, so unless people
object, I'll implement that solution: a Java null value to a dynamic
set role parameter effectively sets the role to NONE (no current role
set). A dynamic parameter string of "NONE" will be interpreted as a
role called NONE.

BTW: GR2 requires that we trim away blanks at both ends of a string
value before applying it. I don't do that presently for SET ROLE,
because neither does SET SCHEMA. Do we want to become conformant on
this detail?  Unless we prohibit delimited identifiers from having
leading or trailing spaces, its seems unwise do do it. We don't
presently prohibit that, nor could I find support for prohibiting it
in the standard, checking syntax rules in §5.2 (Token and separator).

> SQL roles: add catalog support
> ------------------------------
>                 Key: DERBY-3137
>                 URL: https://issues.apache.org/jira/browse/DERBY-3137
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>         Attachments: DERBY-3137.diff, DERBY-3137.diff, DERBY-3137.stat, DERBY-3137.txt
> As a next step after adding support for the roles syntax, I intend to
> make a patch which implements catalog support for roles,
> cf. SYS.SYSROLES described in the specification (attached to
> DERBY-2207). Also the patch should tie this support up to the parser
> support, so the role statements can be executed. Any privileges
> granted to roles would still have no effect at run-time.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message