Re: Strange behaviour with exclude / filter and a nullable FK

2009-09-15 Thread Russell Keith-Magee
On Wed, Sep 16, 2009 at 3:19 AM, Marcob wrote: > > On Sep 15, 8:05 pm, Alex Gaynor wrote: > >> This has already been filed as a bug in Django's ticket >> tracker:http://code.djangoproject.com/ticket/10790.  In the future please try >> searching the tracker before filing a bug. > > Thanks Alex,

Re: Strange behaviour with exclude / filter and a nullable FK

2009-09-15 Thread Marcob
On Sep 15, 8:05 pm, Alex Gaynor wrote: > This has already been filed as a bug in Django's ticket > tracker:http://code.djangoproject.com/ticket/10790.  In the future please try > searching the tracker before filing a bug. Thanks Alex, but: 1) I searched the trac 2) I didn't find the bug 3) So

Re: Strange behaviour with exclude / filter and a nullable FK

2009-09-15 Thread Alex Gaynor
On Tue, Sep 15, 2009 at 1:58 PM, Marcob wrote: > > On 15 Set, 19:32, Marcob wrote: > >>     LEFT OUTER JOIN "auth_user" ON ("ticket_ticket"."assigned_id" = > > I translated from italian, obviously assigned_id should be > assigned_to_id. > > Sorry. > > Ciao. > Marco. > > > > This has already bee

Re: Strange behaviour with exclude / filter and a nullable FK

2009-09-15 Thread Marcob
On 15 Set, 19:32, Marcob wrote: >     LEFT OUTER JOIN "auth_user" ON ("ticket_ticket"."assigned_id" = I translated from italian, obviously assigned_id should be assigned_to_id. Sorry. Ciao. Marco. --~--~-~--~~~---~--~~ You received this message because you are

Strange behaviour with exclude / filter and a nullable FK

2009-09-15 Thread Marcob
I have a model with a FK on User table: from django.contrib.auth.models import User class Ticket(models.Model): assigned_to = models.ForeignKey(User, null=True, blank=True) ... Then I have these two querysets: >>> q1 = Ticket.objects.filter(assigned_to__isnull=True)