Hi all, I'd like to draw your attention to long-open ticket #3871 [1].
The idea is to let ORM users choose which custom manager to use for reverse "many" relations, i.e. reverse foreign key (…_set) as well as forward and reverse many-to-many relations. There are several proposed patches to this ticket, the latest was added by me a week ago. The current implementation adds a "manager()" method to the reverse manager which allows you to pick a manager different from the default one on the related model. All changes are entirely backwards-compatible – if you don't call the "manager()" method, everything is as before, i.e. the default manager is used to look up related model instances. During my review of the previous patch I found that it doesn't apply cleanly to trunk, as well as some concerns with regard to the general approach of the implementation. Therefore, I wrote an alternative patch which is currently awaiting review. Since I wrote that patch, I cannot review it myself. If you can spare some time, maybe you can take a look at it and if you feel the current approach is okay, bump the ticket to "ready for check-in". Of course feel free to raise any concerns you might have. Regards, Sebastian. PS: Merry X-Mas and whatnot! :D [1] https://code.djangoproject.com/ticket/3871 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
