On Tue, Nov 9, 2010 at 5:33 PM, Prabath Siriwardana <prab...@wso2.com>wrote:
> Also if we look at this particular operation where the system > deadlocked - you find the following in the code.. > > DatabaseUtil.updateDatabase(dbConnection, > > DBConstants.ON_DELETE_PERMISSION_UM_ROLE_PERMISSIONS_SQL, resourceId, > tenantId); > DatabaseUtil.updateDatabase(dbConnection, > > DBConstants.ON_DELETE_PERMISSION_UM_USER_PERMISSIONS_SQL, resourceId, > tenantId); > DatabaseUtil.updateDatabase(dbConnection, > DBConstants.DELETE_PERMISSION_SQL, > resourceId, tenantId); > > Here there there database operations executed sequentially - in fact > using a Triger on delete - we could minimize it to one and improve the > performance - discussed with Sumedha and this is something possible we > could do... > > But have been avoiding due to logic getting split between application code & database script. But this would bring about a good performance. /sumedha > Thanks & regards, > -Prabath > > On Tue, Nov 9, 2010 at 5:20 PM, Prabath Siriwardana <prab...@wso2.com> > wrote: > > On Tue, Nov 9, 2010 at 5:13 PM, Samisa Abeysinghe <sam...@wso2.com> > wrote: > > > >>> > >>> 1. addAuthorizationForRole > >>> 2 clearRoleAuthorization > >>> 3. clearRoleActionOnAllResources > >>> 4. resetPermissionOnUpdateRole > > > > 5. clearResourceAuthorizations > > > > Thanks & regards, > > -Prabath > > _______________________________________________ > Stratos-dev mailing list > stratos-...@wso2.org > https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
