Re: Model tree in relational database with property inheritance

From: -CELKO- <jcelko212_at_earthlink.net>
Date: Sun, 6 Jan 2019 10:52:43 -0800 (PST)
Message-ID: <17452ac1-08fa-4924-ab0e-bbeea51fb251_at_googlegroups.com>


I designed a system so that meets your description years ago using a nested set model. It was for access control, and controlled permissions on software. Basically the higher levels in the tree, you were given access to software packages that apply to your department, project team or whatever organizational aggregate was appropriate. So at one level. Maybe all employees had access to the company email, while the guys in the engineering department had access to the daily Dilbert cartoon strips, but as you went down to a particular project team they could only see the software that belong to that project. The only bad part of it was there was no good way to exclude people except one employee at a time. The nodes in the tree were basically a list of software, with flags as to what level of access they had.

It wasn't really that hard to design once we got the basic principle. Received on Sun Jan 06 2019 - 19:52:43 CET

Original text of this message