Related Managers and use_for_related_fields strangeness

2009-06-04 Thread Streamweaver
I'm still struggling a bit with related managers. I have what I think should work right by the documentation but behavior isn't as expect. I've pasted the actual code below but the basic deal is this. I have a Project model which has Releases so Releases have a FK field for Projects. I want to

Re: Related Managers and use_for_related_fields strangeness

2009-06-06 Thread Streamweaver
No insights at all in the group? --~--~-~--~~~---~--~~ 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

Re: Related Managers and use_for_related_fields strangeness

2009-06-06 Thread Streamweaver
Cutting down the code sample I gave above in case that helps. Code snippet below Again, my problem is that if I call Release.objects.planning_backlog() it works and I get all relavant Releases. If I call Project.release_set.planning_backlog() I again get all Releases that fit the filter instead

Re: Related Managers and use_for_related_fields strangeness

2009-06-06 Thread Ramiro Morales
On Thu, Jun 4, 2009 at 11:41 PM, Streamweaver wrote: > > I'm still struggling a bit with related managers.  I have what I think > should work right by the documentation but behavior isn't as expect. > > [...] > > I have a Project model which has Releases so Releases have a FK field > for Projects.

Re: Related Managers and use_for_related_fields strangeness

2009-06-06 Thread Streamweaver
I'll have to look harder at the documentation then as I'm a bit confuesed. What I thought was happening was that I would get a Project object (p) by filtering. I thought p.release_set returned a query set of Release filtered to those related to that project and I could just continue to filter do

Re: Related Managers and use_for_related_fields strangeness

2009-06-10 Thread Ramiro Morales
On Sun, Jun 7, 2009 at 12:44 AM, Streamweaver wrote: > > I'll have to look harder at the documentation then as I'm a bit > confuesed. > > What I thought was happening was that I would get a Project object (p) > by filtering. > > I thought p.release_set returned a query set of Release filtered to >