On Wed, May 21, 2008 at 01:41:35PM -0500, James Bennett wrote: > Note that this is, for example, how Django's User model works: you > relate another model to it with a good old-fashioned foreign key, and > there's a nice API for specifying which model represents the "user > profile" for a given site. You could emulate that for your own models > quite easily.
This brings up something I don't quite get: Django provides user.get_profile(), but the ORM makes it just as easy to say user.userprofile (assuming your profile model is called "UserProfile"). Is there any reason to set up and use user_get_profile() instead? -Jeremy P.S. Since I almost never post, I'd like to add a huge THANK YOU to all the contributors for Django, which I use just about every day and with which I have built many projects. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
