On 10/13/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Ticket #2253 is in the process of being fixed as part of a larger
> change, so micro tweaks as you are suggesting, whilst they may or may
> not fix #2253 are going to be swallowed up in the changes (it's one of
> the test cases for the n
On Sat, 2006-10-14 at 03:27 +, afarnham wrote:
> Ok, so I looked at the SQL and it is a huge statement. Once I work out
> what it is doing I may post it here. However, I may just go with a
> straight sql query here and bypass the ORM until these new changes are
> implemented. Any idea of a tim
Ok, so I looked at the SQL and it is a huge statement. Once I work out
what it is doing I may post it here. However, I may just go with a
straight sql query here and bypass the ORM until these new changes are
implemented. Any idea of a time frame on when those will be up for
testing? I will be hap
On Fri, 2006-10-13 at 20:04 +, afarnham wrote:
> Hi all,
>
> I am having trouble with a Q object look up in one of my apps. When I
> execute the following:
>
> Tag.objects.filter(Q(card__owner = u)|Q(usercardmeta__user = u))
>
> an empty queryset is returned. The filtered QuerySet should be
Hi all,
I am having trouble with a Q object look up in one of my apps. When I
execute the following:
Tag.objects.filter(Q(card__owner = u)|Q(usercardmeta__user = u))
an empty queryset is returned. The filtered QuerySet should be
returning this list:
[, , , ]
After stepping through and grokkin
