Hey Marcus, Thanks for the ideas. I haven't tested it, but the second solution is specifically mentioned as not working in the docs:
https://docs.djangoproject.com/en/1.7/topics/db/managers/#set-use-for-related-fields-when-you-define-the-class Your first solution is what I have in place now (specifically, I have a little function that makes the manager using the solution you describe), and it does work. This isn't a pressing need by any measure, it would just clean up the code a little and I thought it would make sense that as_manager should be able to make a manager with any basic manager behavior. Regards, Martin -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAD_p8v2tb-d6YQBqON63mP7m1S73FXTUXbY_-y2VOqsiRnMLiQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
