diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2018-01-25 16:14:54 -0500 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2018-01-25 16:15:29 -0500 |
| commit | 3996c8021cdd2db87084782f1b929e45bdc6418e (patch) | |
| tree | cd02634887c8cc5802fe254f653d1277ffcc3315 | |
| parent | 296dc0effe97c9b59e6766f936b0bca9a69e19b2 (diff) | |
| download | sqlalchemy-3996c8021cdd2db87084782f1b929e45bdc6418e.tar.gz | |
Add note to FAQ that IN behavior is modernized in 1.2.
Change-Id: Ibe05d8aaa8da90b52cd07f3bce89dcbd49b841c9
(cherry picked from commit 80e1e8b4a54b6ceeeebec46bdf822069a6ef8df3)
| -rw-r--r-- | doc/build/faq/sqlexpressions.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/build/faq/sqlexpressions.rst b/doc/build/faq/sqlexpressions.rst index c3504218b..8b13baeb3 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:: |