On Feb 18, 11:28 am, Aymeric Augustin <aymeric.augus...@polytechnique.org> wrote: > Hello, > > 1.4 beta arrived a bit late, but we'd like to catch up and release RC1 before > the end of the month. > > Until then, we're going to focus on: > > 1 - Release > blockers:https://code.djangoproject.com/query?status=!closed&severity=Release%...
There are two release blockers related to the new prefetch_related feature which needs some attention. The first one is out of my comfort zone: it is about what DB to use for prefetching when .using() has been called for the main queryset. Currently the database which happens to be in use for the related queryset will be used. That is, the main queryset's .using() has no direct effect for the prefetch. Maybe use the database of the main queryset if the related queryset doesn't _explicitly_ use any database? I really don't know this area. I checked the original ticket for prefetch_related and the conclusion there was that lets leave this for later, we don't know this area. Any multidb-people willing to help? The ticket is #17696. The second one is about .iterator() and .prefetch_related() interoperability. They are mutually exclusive (you need to fetch all the objects before you can do prefetch. However, .iterator() says do not fetch all the objects in one go...). There are basically three ways forward: raise an error, favor .iterator() (current behavior) or favor .prefetch_related(). I think each one has some merit, and this is mostly bike-shedding. However, if you have good reasons for one of the options it would be good to hear them now. I would prefer either error or doing the prefetch even when iterator is used. As I don't recall ever actually using .iterator() in production I have no strong opinions. The ticket is #17668. - Anssi -- 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.
