add a direct mapping when using ForeignKey fields with unique=True in place of the deprecated OneToOneField
|Reported by:||mrmachine <real dot human at mrmachine dot net>||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||master|
|Cc:||real.human@…||Triage Stage:||Design decision needed|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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().
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.
Change History (3)
comment:1 Changed 10 years ago by Simon G. <dev@…>
- Component changed from Uncategorized to Database wrapper
- Needs documentation unset
- Needs tests unset
- Owner changed from jacob to adrian
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Design decision needed