Closed GoogleCodeExporter closed 9 years ago
I solved the specific problem here reported but I still think it would be
useful the
possibility to give a queryset rather than a model to usage_for_model.
Thanks again
Francesco
Original comment by fd.calab...@gmail.com
on 3 Mar 2008 at 10:28
Hi again,
sorry if I insist on this issue, I don't mean in any way to depreciate the
value of
this awesome application. I just want to say that I came again across a
situation
where it would have been quite useful to pass a queryset as parameter rather
than
using the filters parameter. The obvious general case is when you have a custom
manager (say something like Blogs.objects.live()) and you would like to pass the
queryset returned by such manager rather than repeating in the filters
parameter the
same logic you have in the managers. Moreover in some cases the django ORM is
simply
not enough to handle all the cases.
Thanks again
Francesco
Original comment by fd.calab...@gmail.com
on 8 Mar 2008 at 4:06
Looking at teh code the object manager supports:
Tag.objects.usage_for_queryset()
Closing the request.
Original comment by doug.nap...@gmail.com
on 12 Aug 2008 at 6:00
Original issue reported on code.google.com by
fd.calab...@gmail.com
on 24 Feb 2008 at 10:02