From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Thu, 25 Jan 2018 21:14:54 +0000 (-0500)
Subject: Add note to FAQ that IN behavior is modernized in 1.2.
X-Git-Tag: rel_1_1_16~10
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=80e1e8b4a54b6ceeeebec46bdf822069a6ef8df3;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

Add note to FAQ that IN behavior is modernized in 1.2.

Change-Id: Ibe05d8aaa8da90b52cd07f3bce89dcbd49b841c9
---

diff --git a/doc/build/faq/sqlexpressions.rst b/doc/build/faq/sqlexpressions.rst
index e81455602c..f65485fbe0 100644
--- a/doc/build/faq/sqlexpressions.rst
+++ b/doc/build/faq/sqlexpressions.rst
@@ -91,6 +91,10 @@ producing output like::
 Why does ``.col.in_([])`` Produce ``col != col``? Why not ``1=0``?
 -------------------------------------------------------------------
 
+.. note:: This section refers to SQLAlchemy 1.1 and earlier.  The behavior has
+   been revised in version 1.2 of SQLAlchemy to actually produce ``1=0`` in
+   the default case.
+
 A little introduction to the issue. The IN operator in SQL, given a list of
 elements to compare against a column, generally does not accept an empty list,
 that is while it is valid to say::