#15200: ManyToManyField combined with "|" leads to trouble
-----------------------------------------+----------------------------------
Reporter: vanschelven | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: 1.2
Resolution: wontfix | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
-----------------------------------------+----------------------------------
Changes (by russellm):
* status: reopened => closed
* resolution: => wontfix
Comment:
Yes, but the issue is that it's a *documented* leaky abstraction, and one
that is very difficult to avoid without imposing a large computational
overhead -- which is why the leaky abstraction exists.
Trust me -- we've thought about this. That's why it's a documented leaky
abstraction. If you want to advocate for a different, less leaky
interpretation, feel free to raise the issue on django dev. But be warned:
you're not going to get much attention unless you come armed with an
actual solution in the form of working code, or, at the very least, a
general SQL solution to the problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/15200#comment:4>
Django <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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
