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

Rick Hillegas updated DERBY-712:
--------------------------------

    Attachment: catalogs_g.diff

Hi Suran,

Thanks for the new patch, which adds another index to SYSPERMS. After looking 
at dropAllPermDescriptors() again, I realized that I misled you: The while loop 
needs to use 2 indexes. The first is the index you just added--the one which is 
keyed on the id of the privileged object. The second is the original index 
which you were using--the one which is keyed on the unique id of the 
permissions tuple itself. I tweaked dropAllPermDescriptors() accordingly. I 
also tweaked SYSPERMSRowFactory: now that there are 2 indexes, the uniqueness 
array needs to be filled in (one of the indexes is unique, the other isn't). I 
have regenerated the patch and am attaching it as catalogs_g.diff

Am running the regressions tests now. Thanks!

> 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, 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.

Reply via email to