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:
Configuring E-mail (1997)
SPAM is SPAM is SPAM.... Smith Micro - no competition (2000)
Hiding HTML in an [include] file... (2004)
[WebDNA] [BULK] WebDNA 6.2 or 7.x Hosting (might be) Needed (2011)
[subTotal] pricefield in another database !? (1998)
japanese characters (1997)
Webcat/Webmerchant (1998)
WebCat: Paying affiliates commissions?? (2000)
WebCat and WebTV (1997)
Pithy questions on webcommerce & siteedit (1997)
Sorting by type=date (1999)
WebCatalog for Postcards ? (1997)
HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
Hiding HTML and breaking the page (1997)
Today's suggestions (1998)
RE: Automatic Forwarding using WebCat (1997)
Generating Pages (1999)
moved shoppingCarts folder... now there's nothing in it. (2001)
searchable list archive (1997)