#3548: add a direct mapping when using ForeignKey fields with unique=True in 
place
of the deprecated OneToOneField
------------------------------------------------------------+---------------
Reporter:  mrmachine <real dot human at mrmachine dot net>  |       Owner:  
jacob                                        
  Status:  new                                              |   Component:  
Uncategorized                                
 Version:  SVN                                              |    Keywords:  
OneToOne ForeignKey unique direct mapping ORM
   Stage:  Unreviewed                                       |   Has_patch:  0   
                                         
------------------------------------------------------------+---------------
 OneToOneField sets up a direct mapping to the related object in the ORM,
 e.g. when relating Profile in your app to User in contrib.auth, you can
 access the profile with u.profile. as OneToOneField has a few issues and
 is likely going away soon, could we change ForeignKey to add a similar
 user friendly mapping when unique=True is specified, to save having to do
 something like u.profile_set.all()[0].
 
 when only using one model to extend User, you can use the
 AUTH_PROFILE_MODULE setting and the User.get_profile() method, but this is
 specific to User, and indicates the extending model is a "profile", and
 can only be used with one extension of a model. for example, it may be
 possible to have multiple apps within a project, which all share common
 users, but each has specific extensions of User specific to their purpose.
 it's also possible to want to extend other models besides User with a
 OneToOne relation. in those cases, the direct mapping above would come in
 handy. e.g. u.blog_profile, u.intranet_profile, etc.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3548>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to