On 25 March 2013 12:37, Anssi Kääriäinen <[email protected]> wrote:
> I feel pretty strongly that NOT EXISTS semantics are wanted. The NOT > IN semantics are likely there just because that is how the > implementation was originally done, not because there was any decision > to choose those semantics. Most likely, yes, so it looks like a bug fix now not an optimization. > Also, multicolumn NOT IN lookups aren't > supported on all databases (SQLite at least), so for that case NOT > EXISTS semantics is going to happen anyways. Yes, I think that's the clincher. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- You received this message because you are subscribed to the Google Groups "Django developers" 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
