[
https://issues.apache.org/jira/browse/DERBY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727698#action_12727698
]
Suran Jayathilaka commented on DERBY-712:
-----------------------------------------
Hi Rick,
I changed the DataDictionaryImpl.dropAllPermDescriptors() method as follows by
changing the index in the ti.getRow() call to 3, which is the index of the
object Id. I think it should behave correctly now. If this is correct, I will
attach the revised patch when the tests are finished.
public void dropAllPermDescriptors(UUID objectID, TransactionController tc)
throws StandardException {
TabInfoImpl ti = getNonCoreTI(SYSPERMS_CATALOG_NUM);
SYSPERMSRowFactory rf = (SYSPERMSRowFactory) ti.getCatalogRowFactory();
DataValueDescriptor objIdOrderable;
ExecRow curRow;
PermissionsDescriptor perm;
// In Derby authorization mode, permission catalogs may not be present
if (!usesSqlAuthorization)
return;
/* Use objIDOrderable in both start and stop position for scan. */
objIdOrderable = getIDValueAsCHAR(objectID);
/* Set up the start/stop position for the scan */
ExecIndexRow keyRow = exFactory.getIndexableRow(1);
keyRow.setColumn(1, objIdOrderable);
while ((curRow = ti.getRow(tc, keyRow, 3)) != null) {
perm = (PermDescriptor) rf.buildDescriptor(curRow,
(TupleDescriptor) null, this);
removePermEntryInCache(perm);
// Build new key based on UUID and drop the entry as we want to drop
// only this row
ExecIndexRow uuidKey;
uuidKey = rf.buildIndexKeyRow(rf.PERMS_UUID_IDX_NUM, perm);
ti.deleteRow(tc, uuidKey, rf.PERMS_UUID_IDX_NUM);
}
}
Also, when I ran org.apache.derbyTesting.functionTests.tests.derbynet._Suite, I
did not see the failure which you mentioned. I am currently running suites.All
and will check if there are remaining test failures.
Thanks!
Suran
> 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, 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.
