unix permissions theory applied to db security? Or...?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 31582
interpreted = N
texte = Could someone think out loud with me on this- ?I have a main.db with 10,000's of records (possibly 100,000's in the future) and each record can be appended/replaced/deleted by a user belonging to the specific group associated with that record PLUS everyone belonging to a group above him in the hierarchy of groups (but no one in a more lowly group). Imagine a tree with branches and the person at the trunk can edit any record, while the few people at the level of the first branches can edit 75% of the records, while people at the fine twig level can only edit a few records... But the trunk man can of course edit a twig record...I came up with a solution but someone suggested to me that this is really just a permissions issue and so could be more efficiently handled than the way I thought of. Can we apply the priciples of the way unix permissions work to efficiently allow just the security I need for this db? (I have never run a unix box myself...) Or do you have any thoughts on this at all you could share with me?Thanks for the time! :-)-John ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
Could someone think out loud with me on this- ?I have a main.db with 10,000's of records (possibly 100,000's in the future) and each record can be appended/replaced/deleted by a user belonging to the specific group associated with that record PLUS everyone belonging to a group above him in the hierarchy of groups (but no one in a more lowly group). Imagine a tree with branches and the person at the trunk can edit any record, while the few people at the level of the first branches can edit 75% of the records, while people at the fine twig level can only edit a few records... But the trunk man can of course edit a twig record...I came up with a solution but someone suggested to me that this is really just a permissions issue and so could be more efficiently handled than the way I thought of. Can we apply the priciples of the way unix permissions work to efficiently allow just the security I need for this db? (I have never run a unix box myself...) Or do you have any thoughts on this at all you could share with me?Thanks for the time! :-)-John ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
John Butler
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
email preferences on NT (1997)
[shownext] and descending order (1997)
shownext not showing next...still r2 (1997)
wierd [cart] action! (1997)
Questions (1998)
Newspaper Portal (2005)
[include] and not found (2005)
[OT] Helllllooooooo.... (2002)
dos bug? (1999)
[WebDNA] WebDNA future (2010)
no [search] with NT (1997)
Working with framesets (1998)
WebCat2b12--[searchstring] bug (1997)
[WebDNA] Zpanel & WebDNA (2013)
Free shipping (2000)
osx or redhat and / or other (2005)
Archive (Zip, Sit, Tgz) (2004)
Nesting format tags (1997)
Search/sort in URL Was: GuestBook example (1997)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)