#5537: Remove Reverse Lookups on ForeignKeys/ManyToMany
-----------------------+----------------------------------------------------
Reporter: dcramer | Owner: nobody
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------+----------------------------------------------------
Comment (by russellm):
Ah... yeah... that... oops. Missed the great big honking backwards
incompatibility. Scratch that idea :-)
One alternative would be to define a NO_REVERSE string that can act as a
marker for those fields you don't want to have reverse relations.
related_name=NO_REVERSE isn't quite as clean as related_name=None, but it
would avoid the backwards incompatibility problem.
However, I'm happy to go with consensus/BDFL judgement on this. I'm still
in favour of the general feature, but obviously not at the expense of a
clean interface. I also wouldn't lose any sleep if it wasn't implemented,
because there _is_ a workaround.
--
Ticket URL: <http://code.djangoproject.com/ticket/5537#comment:5>
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
-~----------~----~----~----~------~----~------~--~---
