class UserExtensions(object):
blah_field = models.DateField()

User.__bases__ += (UserExtentions,)

I’m guessing that wouldn’t work, though it might depend on how, and what order, syncdb builds tables?

I could just be completely off-base, too. I’m still fairly new to Django.

I like the trick/hack and perhaps the way to avoid some suprises if the Django framwors someday uses the same funtion name could be writing some unit tests for the model that could test the existance of the function.

Other trick, you can use another language to write the hack extensions, for example I would use a name something like get_nombreCorto in Spanish or get_NomCurt in Catalan. The chances that Django some day could use that names are very, very low So, its a nice trick for me.

Thank you.

Your final result would then look something like:

u = User.objects.get(id=3)
u.get_profile().get_shortcut()

See http://www.b-list.org/weblog/2006/06/06/django-tips-extending-user-model for the best explanation of this technique.

Seriously, there is a problem of course when the framework adds a function with the same name, definitely. I got to think about that.

Though I see the solution I posted as valid, as long as you don’t mess with the actual User class internals, in whichever way.

The suggested adapter way is of course viable, but i think it adds another class, which actually should not be needed. Instead I think the framework needs to offer the extending mechanism, if default class-extending is occupied otherwise.

@Ben, model inheritance is supposed to do the following:

class Place(models.Model):
    name = models.CharField(maxlength=50)

class Restaurant(Place):
    description = models.TextField()

class ItalianRestaurant(Restaurant):
    has_decent_gnocchi = models.BooleanField()

I can not tell if that is the right path, my gut feeling says no, but thats very subjective!
and described here http://code.djangoproject.com/wiki/ModelInheritance

Could you explain that a bit more? I’m new to django…