I have produced a patch for this [1] long-standing SQL bug. The SQL produced with the patch is correct AFAIK, but my understanding of the sql code is rather poor so I'm hoping that someone who knows better will give it a look. There might be a more correct/elegant way to fix this.
[1] http://code.djangoproject.com/ticket/12823 Best regards, Philippe -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
