Hello, I'm afraid I'll have to reply to my own message because nobody else did. ;) Please read on. Also, please note that the original report is now over five weeks old, with no real solution yet in sight.
On Thu, 29 Sep 2011 21:52:23 +0200 Sebastian Goll <sebastian.g...@gmx.de> wrote: > I'd like to draw your attention to ticket #16715: > > "Wrong JOIN with nested null-able foreign keys" > https://code.djangoproject.com/ticket/16715 I think this is a serious bug which should be further investigated. There is the possibility that also other queries do not work as expected, when multiple models with (null-able) foreign keys are involved. Can somebody please tell me if the latest test I supplied is valid ("nested-foreign-key-test-r16914.patch")? I'd like to get the confirmation that this is indeed a bug and not somehow intended behavior. If this is indeed a bug, what would be the best way to fix it? Unfortunately, I'm not fluent in the internals of the Django query generator, so at least some help is required here. In fact, any help in resolving this issue is greatly appreciated. For a summary, please see my original post to this list (in case you didn't receive it): "Wrong JOIN with nested FKs" http://groups.google.com/group/django-developers/msg/4c5dcff7beaf06d9 Sebastian. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
