PublicArchive/sqlalchemy
2
0
Fork 0
mirror of https://github.com/sqlalchemy/sqlalchemy.git synced 2026-05-27 19:15:05 -04:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
Change-Id: Ibe05d8aaa8da90b52cd07f3bce89dcbd49b841c9
This commit is contained in:
Mike Bayer
2018-01-25 16:14:54 -05:00
parent 6ae587b59f
commit 80e1e8b4a5
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/build/faq/sqlexpressions.rst
Vendored
+4
View File
@@ -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::