[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-712:
--------------------------------
Attachment: derby-712-02-aa-privilegeNodeCleanup.diff
Attaching derby-712-02-aa-privilegeNodeCleanup.diff. This slightly reworks the
code in PrivilegeNode so that it will be easier to add the USAGE privilege.
GrantRevokeDDLTest runs cleanly. I intend to commit this patch if the full
regression tests pass.
This patch makes the following changes:
1) Abstracts out the notion of a qualified objectName, which is common to all
privileges.
2) Moves the self-revoke check outside the individual bind() cases so that it
doesn't have to be repeated for each case.
3) Adds braces around dangling conditional consequences because, in my
experience, unbraced single-line consequences are a brittle source of bugs.
Touches the following file:
M java/engine/org/apache/derby/impl/sql/compile/PrivilegeNode.java
> Support for sequences
> ---------------------
>
> Key: DERBY-712
> URL: https://issues.apache.org/jira/browse/DERBY-712
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Environment: feature request
> Reporter: Tony Dahbura
> Assignee: Suran Jayathilaka
> Fix For: 10.6.0.0
>
> Attachments: altertable.diff, catalogs_a.patch, catalogs_b.patch,
> catalogs_c.patch, catalogs_d.patch, catalogs_e.patch, catalogs_f.patch,
> catalogs_f_2.patch, catalogs_g.diff, catalogs_h.diff,
> create_drop_sequence_a.patch, create_drop_sequence_b.patch,
> create_drop_sequence_c.patch, create_drop_sequence_d.patch,
> create_sequence_a.patch, derby-712-02-aa-privilegeNodeCleanup.diff,
> SequenceGenerator.html
>
>
> Would like to see support added for sequences. This would permit a select
> against the sequence to always obtain a ever increasing/decreasing value.
> The identity column works fine but there are times for applications where the
> application needs to obtain the sequence number and use it prior to the
> database write. Subsequent calls to the table/column would result in a new
> number on each call.
> SQL such as the following:
> SELECT NEXT VALUE FOR sequence_name FROM sometable ; would result in a next
> value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
