Hi all, I've recently been using the __in filter, and it's pretty nifty. However, it seems that nesting any of geodjango's spatial filters with the __in filter is busted. This ticket: https://code.djangoproject.com/ticket/17314 explains the behavior in detail, but the précis is: "things = Thing.objects.filter(point_field__contained=Polygon(...))" followed by "other_things = OtherThing.objects.filter(thing__in=things)" results in the sql compiler blowing up when the query for other_things is supposed run.
This is a major pain in two apps I'm working on, and I'll sponsor patches with things including but not limited to: * Free beer * Homemade cupcakes * Hugs Or, if you have the inhuman inclination to refuse the aforementioned bribery, I can probably fix the issue with some direction (which would still be met with considerable gratitude). Thanks, jpk -- John P. Kiffmeyer Email/XMPP: j...@thekiffmeyer.org -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
