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...
Thanks & regards,
-Prabath
On Tue, Nov 9, 2010 at 5:20 PM, Prabath Siriwardana <[email protected]> wrote:
> On Tue, Nov 9, 2010 at 5:13 PM, Samisa Abeysinghe <[email protected]> wrote:
>
>>>
>>> 1. addAuthorizationForRole
>>> 2 clearRoleAuthorization
>>> 3. clearRoleActionOnAllResources
>>> 4. resetPermissionOnUpdateRole
>
> 5. clearResourceAuthorizations
>
> Thanks & regards,
> -Prabath
_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
