[
https://issues.apache.org/jira/browse/DERBY-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-3073:
---------------------------------
Attachment: DERBY-3073-part-2.diff
This small patch, DERBY-3073-part-2, adds the following to the parser:
- check that role identifiers are max 30. Until the restriction of max
30 is lifted for user identifiers, role identifier should follow
suit, since both are authorization identifiers. Role identifiers
will be present along with user identifiers in the permission
catalogs, for which the limit is documented as 30.
- add the possibility that SET ROLE can take a string argument.
Presently, it accepts an identifier, a dynamic parameter
marker('?') or NONE.
Actually, the SQL standard specifies that both SET ROLE and SET
SCHEMA should take <value specification>, which *precludes* the use
on an identifier argument. But since SET SCHEMA is liberal, I elect
to make SET ROLE liberal too (keeping the possibility to specify
an identifier).
An extra test case for SET ROLE <string> is also added. Not for commit yet,
running tests.
> SQL roles: add parser support
> -----------------------------
>
> Key: DERBY-3073
> URL: https://issues.apache.org/jira/browse/DERBY-3073
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Fix For: 10.4.0.0
>
> Attachments: DERBY-3073-part-2.diff, DERBY-3073.diff,
> DERBY-3073.stat, DERBY-3073b.diff, DERBY-3073b.diff, DERBY-3073b.stat,
> DERBY-3073b.stat, DERBY-3073c.diff, DERBY-3073c.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
