Geek asks and answers

The right way to design an inventory system

I'm a pretty good programmer, but I'm not very good when it comes to developing system architectures. I have a pretty simple inventory system that I create, but I would like to know a good way to structure it.

I have about 20 pieces of equipment that users can [View all | Update | Delete | Add] each of them. However, I have different access levels for different equipment (which should be dynamic, change who can view or delete what).

For example, would one subject have?

addPart1.php
removePart1.php
updatePart1.php
index.php (view all parts)

addPart2.php
removePart2.php
updatePart2.php
index.php (view all parts)

For all parts? Im confused in trying to create a nice, scalable and efficient structure.

+3
source share
2

(ACL) - , . ACL , , . ACL (, (, ) ACL WXY WXY).

: WIKI

, :

http://dev.juokaz.com/php/acl-made-easy-part-1 ( ACL)

http://sourceforge.net/projects/tackle/

+6

, "" "". , "group_id" ( ). 300 , 1, - 2 ..

, (, / ), "group_permissions". " ", . , .

$permissions = '1,2,5,9';

, PHP, :

SELECT * FROM products WHERE group_id IN($permissions)

, . .

+1

More articles:


All Articles