Like I said use the "Groups" and then like what was suggested "Permissions". That should handle what your are trying to do and not introduce any conflicts.
On Aug 18, 9:17 am, dfolland <dfoll...@nex-tech.com> wrote: > Try using "Groups" that is part of the Django user authentication. > > https://docs.djangoproject.com/en/dev/topics/auth/ > > On Aug 18, 6:56 am, Cameron <cameronma...@gmail.com> wrote: > > > > > > > > > Hi, I'm wondering if anyone can help shed some light on the best > > approach is too creating different Users. I'm trying to make a online > > shop, that features two types of Users, "Customers" and "Merchants". > > The power of each Users vary greatly, Customers can buy items from > > Merchants and Merchants can (as you would expect) list new products, > > edit them. Merchants required additional information compared to > > Customers (such as Address, Contact Info, Payment details). > > > Now hows the best way to handle this? I've read that subclassing the > > User class is bad (I'm not entirely sure why though). Most examples > > try to extend the User class, with a UserProfile class with a OneToOne > > relationship to the User class (like thishttp://pastebin.com/GQVLrVTx). > > Is it better to extend that to a UserProfileMerchant and > > UserProfileCustomer, or have a single UserProfile, and have a boolean > > field to indicate if the account is a Merchant? (both examples in the > > following -http://pastebin.com/F8ZenCa1) > > > Any advice on the matter would be greatly appreciated! -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
