I have recently worked through a similar problem. I'm building a site to manage characters, and the organizational structure of a military unit in a game I run in my spare time. In my case i wanted to have one table to store all of the organizational levels (I called them divisions), with a type field that helped determine what level they were at. I then had a position table which stored the various position names, and also linked them to a particular division and a character. Thus each character could have multiple positions, in different divisions.
What I'm not sure about is whether this would work for your situation. You said you think the structure is like this Example: CEO ---> Directors ----> Managers ---> Individual contributors. If you don't have unit divisions within your unit, you could substitute each position into the tree with a parent ID pointing up, and then have a link table that would allow the individual to have or report to many. In my case, I was torn between putting the semantics of the Positions into the Tree's at a level below their respective divisions, and then only attaching characters there, but I really felt that was not a good idea for my current project. If an employee can serve multiple positions and report to multiple people, it almost sounds like you might need one table for the position -> Character relationship, and another to store the character to multiple character/managers. I guess it depends on how much complexity you need. Hope this gives you some ideas. Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
