Users not spanning relationship lookups
|Reported by:||Streamweaver||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||1.0|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Description (last modified by )
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.