Users not spanning relationship lookups

[Streamweaver]

I believe there may be a bug related to relationship spanning as relates to User models.

I'm using python 2.6 and Django 1.0.2 and this is consistant across Window and Linux installs.

I have to Models both with relationships to Users, cutting down to relavant parts:

class Project(models.Model):
    owner = models.ForeignKey(User)

class Release(models.Model):
     owner = models.ForeignKey(User)

In my view methods when I use:

u = User.objects.exclude(project__owner__isnull=True, release__owner__isnull=True).distinct()

it returns an error of "no such column: U1.owner_id"

Alternatively when I try:

u = User.objects.filter(project__owner__isnull=False).distinct() | User.objects.filter(project__owner__isnull=False).distinct()

This returns a list of ALL users regardless being an owner of a project or release. Using either of those queries alone also returns all users.

I've checked and checked and this is setup as documented and I believe is a bug. I asked on Django-Users, they believe this is a bug as well.

[Streamweaver]

Argh, the formatter removed underscores from the Code I pasted, sorry about that. The example code that does not work is as follows:

u = User.objects.exclude(project__owner__isnull=True, release__owner__isnull=True).distinct()
u = User.objects.filter(project__owner__isnull=False).distinct() | User.objects.filter(project__owner__isnull=False).distinct()

[Ramiro Morales]

(reformatted description)

[Russell Keith-Magee]

"They" don't believe this is a bug. "They" didn't answer your question before you posted the ticket. There is a very important difference.

This isn't a bug - it's expected behavior. See the mailing list thread for the reason.