I have been much reading on rbac. A typical rbac sql database schema is described to have...
Users -> Roles -> Permissions structure that act on objects (ie. tables) in a database. This I am fine with (I think)
My question is about permissions given to each row in a resource like tblNews table in order to protect it. So from a Users perspective...
Users Permission = I can edit each row in the tblNews table where the assigned editors of any row are USERTYPE_X
and from the tblNews perspective...
tblNews Permission = This rows editors are USERTYPE_X and USERTYPE_Y
i.e. the data in any one row of a resource is itself protected by a combination of PermissionType (CAN_EDIT_NEWS) and UserType (Club Secretary).
So, rather than a table get protected, it is each row that gets protected.
I hope this makes sense and if you know where I am trying to get to I will appreciate any thoughts and feedback.
there is no direct facility for row level permission. however, you can do it manually, like create few groups for permission, assign every user to one or more group, when you insert the row, create one
With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.
This article is intended for those who are new to PHP error handling (https://www.experts-exchange.com/articles/11769/And-by-the-way-I-am-New-to-PHP.html). It addresses one of the most common problems that plague beginning PHP develop…
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables.
Make a table:
Update a specific column given a specific row using the UPDATE statement:
Remove a set of values using the DELETE s…