Jump to content
Larry Ullman's Book Forums

erik.belusic

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About erik.belusic

  • Rank
    Newbie
  1. thanks for the quick response and all the help so far larry! just to clarify, you believe i should have a buy table, with a buyer model and also a seller table with a seller model? if this is the case, how would i organize the authentication process? i would need to make sure "/seller/profile/update is denied to guests (easy) and someone logged in as a buyer? i know there are isGuest() and a corresponding function for authenticated. how do i handle this with two separate tables and models? can i have two separate classes for authenticating, one for each? for the "admins" i was thin
  2. Yes, they would use the same type of credentials, ie username/password, however I am open to using separate login forms if need be.
  3. that is correct, in this scenario, the sellers wouldn't be individual people, but groups of people or companies. if the individual members wanted to make purchases, they would create a standard buyer/customer account.
  4. i just purchased the yii book, and just started developing an application with yii. the application calls for multiple user account types, and multiple user portals. the basic account types would be admin, seller, buyer. i am looking for the best way (best practice) to set this up. i was thinking there would be one users table, and then a seller table and a buyer table. the reason for separate tables would be that we would be storing different information about the users and the buyers. this then makes users have a 1:1 relationship with either buyer or seller table. so im still undecid
×
×
  • Create New...