> You can have your doubts if you like. I don't think they're correct.
> Indeed "when it is ready" is the very definition of "reasonable time".
Nice reply :-)
>
> > How can we now solve the task of "how to find rows in a table that
> > have no counterpart in another table" ?
>
> This is already
Hello Malcolm.
What is your estimation on merging your queryset-refactor branch?
Now INNER JOIN isnull lookup parameter does not work for related
models because INNER JOIN produce cartesian product between the
specified tables (that is, each and every row in the first table is
joined to each and
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.
see in documentation any examples on how to use generic
relation for lookups so may be nobody is using it? :-)
SHALL I CREATE A TICKET!?
On Nov 29, 12:34 pm, Litnimax <[EMAIL PROTECTED]> wrote:
> Main question is why do we have 2 JOINS instead of one?
> And 2-nd inner join is appar
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
| 1 | 1000 |
| 46337 | 13 | 2 | 1020 |
+---+-+-+----+
2 rows in set (0.00 sec)
On Nov 29, 3:58 am, Litnimax <[EMAIL PROTECTED]> wrote:
> Hello dear Django developers!
>
> Can GenericRelation be used for the following lookup
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
