Hello,
akaariai has proposed a patch that solves the bug described below.
It is attached to ticket #16715. How do we proceed from here?
Sebastian.
On Thu, 29 Sep 2011 21:52:23 +0200
Sebastian Goll wrote:
> Hello,
>
> I'd like to draw your attention to ticket #16715:
2011/10/3 Łukasz Langa :
> Wiadomość napisana przez Russell Keith-Magee w dniu 3 paź 2011, o godz.
> 16:07:
>
> 1) Build your own experience with the internals of the ORM. As part
> of this learning process, document what you learn -- we would very
> much like to have better
Wiadomość napisana przez Russell Keith-Magee w dniu 3 paź 2011, o godz. 16:07:
> 1) Build your own experience with the internals of the ORM. As part
> of this learning process, document what you learn -- we would very
> much like to have better documentation of the internals of Django's
> ORM,
On Mon, Oct 3, 2011 at 2:40 AM, Sebastian Goll wrote:
> 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.
>
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" gro
Hello,
I'd like to draw your attention to ticket #16715:
"Wrong JOIN with nested null-able foreign keys"
https://code.djangoproject.com/ticket/16715
It seems that the Django query generator sometimes picks the wrong join type in
the following situation:
Model A
| (Relation A/B: