Ticket created - http://code.djangoproject.com/ticket/6051
Regards,
Max.
--~--~-~--~~~---~--~~
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.
May be I was not clear may be I do not understand something or maybe I
am not understood?
Anyway here is the patch:
svn diff generic.py
Index: generic.py
===
--- generic.py (revision 6723)
+++ generic.py (working copy)
@@ -118,7 +1
Main question is why do we have 2 JOINS instead of one?
And 2-nd inner join is apparently broken :-(
Regards,
Max.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, se
I did some more investigations and seems I have found a bug probably
related to
http://groups.google.com/group/django-developers/browse_thread/thread/53c9d7d877c318bd.
This is 100% bug.
The example below uses same models as in previous post.
print
LocalNumber.objects.filter(subscription__accoun
Hello dear Django developers!
Can GenericRelation be used for the following lookup example?
Here subscription is .GenericRelation field name (see model
definitions below).
user_numbers =
LocalNumber.objects.filter(subscription__account=user_account)
I bet it WORKED! But today I noticed this cod
