#3871: Use custom managers in reverse relations
----------------------+-----------------------------------------------------
Reporter: EspenG | Owner: adrian
Status: new | Component: Core framework
Version: SVN | Resolution:
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------+-----------------------------------------------------
Changes (by Jeff Forcier <[EMAIL PROTECTED]>):
* cc: [EMAIL PROTECTED] (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I believe someone also came up with a suggestion of selecting the Manager
for a given !ForeignKey relationship via the FK definition itself - e.g.
`foo = ForeignKey(Foo,manager=Foo.manager2)`. I'm thinking something
"clever" like `ForeignKey(Foo.manager2)` would be nicely succinct and
could preserve backwards compatibility by assuming the default Manager if
you just pass in the `Foo` class.
However, that sort of syntax/implementation then locks you into a single
manager; while that's really no worse than how things currently stand, the
`foo.xxx_set_<manager_name>` version would be more flexible, if more
verbose. Ideally there'd be a way to get the best of both worlds.
--
Ticket URL: <http://code.djangoproject.com/ticket/3871#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
