On Wed, May 21, 2008 at 2:00 PM, Jeremy Bornstein <[EMAIL PROTECTED]> wrote:
> 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
On Wed, May 21, 2008 at 3:00 PM, Jeremy Bornstein <[EMAIL PROTECTED]> wrote:
> (assuming your profile model is called "UserProfile")
I think you just answered your own question. Consider a third-party
app that might be used to manage user profiles, but leaves the actual
implementation of that pro
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 si
3 matches
Mail list logo
