Dougal, Thanks for the heads up... looks like I'l user get_profile if only for the the next guy who comes along... :-)
Nicholas. On Mar 17, 11:01 pm, Dougal Matthews <[email protected]> wrote: > get_profile is newer than model inheritance I believe. > Working with profile is how everybody seems to be doing it, so follow the > trend and it'll make every bodies lives easier ;) > > If you really want to read more about it, there is loads of chatter on the > subject so to avoid > reppetition;http://www.google.co.uk/search?q=django+extending+user(granted, > lots of it > is old) > > Dougal > > --- > Dougal Matthews - @d0ugalhttp://www.dougalmatthews.com/ > > 2009/3/17 ntoll <[email protected]> > > > > > Guys, > > > Asking for advice here. > > > What is the best way to extend the User class in > > django.contrib.auth.models...? > > > I could either inherit the class for my own model and add fields / > > methods or use get_profile(). Now, whilst I realise that get_profile() > > is the official advice it seems a tad out-of-date now that there is > > model inheritance (for which get_profile() provided a means of > > overcoming). > > > Pros/cons of each method? To my mind inheriting from User class is > > more elegant... but would love to know your thoughts on this. > > > All the best, > > > ntoll --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
