Thank you for the article and the advice. I decided not to use it because there wasn't a lot of documentation around the web on it and I didn't want to go "all in" on something that is experimental. Again, thanks for the article.
On Mar 13, 2:41 pm, brian <[email protected]> wrote: > On Fri, Mar 13, 2009 at 2:34 PM, Chez17 <[email protected]> wrote: > > > I am trying to code a system with 3 different user levels, admin, > > technicians, and clients. They all have logins and will use the users > > controller. My question is a philosophical one, not a technical one. > > So I have the technicians and clients, for the most part they are > > similar, but they will be doing very different things. Does it make > > sense to create a new model for each? Or just stack everything in the > > User model. What is the best way to define the relationship? A > > Technician belongs to a User? Any help is most appreciated, thanks. > > Whether you use ACL or not, I'd recommend that you create models for > each of these. You can put all of the common stuff (esp. username & > password). How you then associate User with the other models depends > on what you want to do and your preferences, as there are a couple of > options. Have a look at this Bakery article for starters: > > http://bakery.cakephp.org/articles/view/inheritable-behavior-missing-... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
