On Fri, Nov 8, 2013 at 1:44 AM, Robin St.Clair <robin...@live.co.uk> wrote: > The last time I checked the use of IN, all the records from the database in > the query were brought back to the workstation, rather than being processed > on the backend and only the results returned to the workstation.
Django ORM's __in operator tries to use SQL facilities, but depending on the type of object passed, it could read the list of options and pass it explicitly, or it could merge two SQL commands. always check the type of SQL commands generated! (debug toolbar is your friend) i haven't seen it doing a post-retrieve check in python, thought. -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFkDaoRLfeLi%3DWVu5f%3DcyCXRH0x5mr1fbDiV0OzW%2Bn-fpk6uHw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
