I am attempting to use a custom manager for related object access, as documented here<http://docs.djangoproject.com/en/dev/topics/db/managers/#using-managers-for-related-object-access>, but it does not appear to be working properly. Upon accessing the reverse relationship, I am getting an unfiltered queryset result. Using this trimmed down code <http://dpaste.com/hold/96205/>, and assuming that at least one employee is entered, I should be getting an empty queryset on the third lookup demonstrated below, rather than the full queryset:
>>> from models import Employee, Shift >>> e = Employee.objects.get(id=1) >>> s = Shift.objects.create(worked_by=e) >>> s.is_dereferenced = True >>> s.save() >>> Shift.objects.all() [<Shift: Shift object>] >>> Shift.referenced.all() [] >>> e.shifts.all() [<Shift: Shift object>] The documentation that I linked above seems fairly straightforward, so am I missing something obvious here? I'm hesitant to file this as a bug report, because I have not found any mention of similar issues posted, and that leads me to feel that I must be in the wrong. Any help would be appreciated. Thanks! Luke --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
