Re: Best approach to handling different types of Users

Things will break in the sense that, if you add another app that accesses the User model they will only see the original implementation. They won't get your subclass. Other than that, other apps that use the User model should "work" just fine. Unless I'm missing something, and in that case

Re: Best approach to handling different types of Users

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 wrote: > Try using "Groups" that is part of the Django user authentication. > >

Re: Best approach to handling different types of Users

> I hear this a lot that "things will break" if you subclass User. However, I > haven't seen anyone share a concrete example of *how* things go wrong. > > Anyone got a good example to scare the children with? > > Malcolm Yeh, I've heard this quite a bit as well. An example of a scenario this

Re: Best approach to handling different types of Users

On 19 August 2011 03:37, Andre Terra wrote: > Until you install some third party app that accesses > User.objects.all() and then suddenly nothing works as it's supposed > to. > > I hear this a lot that "things will break" if you subclass User. However, I haven't seen anyone

Re: Best approach to handling different types of Users

On Fri, Aug 19, 2011 at 9:27 AM, Andre Terra wrote: > Alright, do what you will. Whatever floats your boat.. > > On Fri, Aug 19, 2011 at 5:12 AM, Matt Schinckel wrote: >> >> On Friday, August 19, 2011 12:07:44 PM UTC+9:30, Andre Terra (airstrike) >>

Re: Best approach to handling different types of Users

Alright, do what you will. Whatever floats your boat.. On Fri, Aug 19, 2011 at 5:12 AM, Matt Schinckel wrote: > > On Friday, August 19, 2011 12:07:44 PM UTC+9:30, Andre Terra (airstrike) > wrote: >> >> Until you install some third party app that accesses >>

Re: Best approach to handling different types of Users

On Friday, August 19, 2011 12:07:44 PM UTC+9:30, Andre Terra (airstrike) wrote: > > Until you install some third party app that accesses > User.objects.all() and then suddenly nothing works as it's supposed > to. > > Why wouldn't it? The User subclasses will still appear in the

Re: Best approach to handling different types of Users

Until you install some third party app that accesses User.objects.all() and then suddenly nothing works as it's supposed to. You can access the User object from its related UserProfile instance and do everything you say from there instead of breaking the convention. Nobody's stopping you from

Re: Best approach to handling different types of Users

Lately, I have been looking at using subclasses of auth.User as a way of segmenting users. This appears (to me, at this stage, anyway) to have several advantages over using the UserProfile approach. * You can have extra attributes on the subclass. For instance, one set of users belong to a

Re: Best approach to handling different types of Users

Do create a UserProfile with an FK to user, but add an FK to Group as well. This way you can take advantage of the existing Permissions application which would allow/deny users access to various parts of your application. Just make sure your views take those permissions into consideration!

Re: Best approach to handling different types of Users

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 wrote: > Hi, I'm wondering if anyone can help shed some light on the best > approach is too creating different Users. I'm

Best approach to handling different types of Users

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