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

- make a note in 1.1 migration notes for ref #4102

Browse Source 
Change-Id: If9edba3af476bc4303246e55d0ecb53009084342
(cherry picked from commit 9ffee8c94a)
This commit is contained in:
Mike Bayer
2017-10-12 11:15:11 -04:00
parent 0071789de1
commit 98c18ae864
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/build/changelog/migration_11.rst
Vendored
+15
View File
@@ -1646,6 +1646,21 @@ with the pure-Python int-to-boolean processor and is more forgiving of
existing data already within the database. Values of None/NULL are as before
retained as None/NULL.
.. note::
this change had an unintended side effect that the interpretation of non-
integer values, such as strings, also changed in behavior such that the
string value ``"0"`` would be interpreted as "true", but only on backends
that don't have a native boolean datatype - on "native boolean" backends
like Postgresql, the string value ``"0"`` is passed directly to the driver
and is interpreted as "false". This is an inconsistency that did not occur
with the previous implementation.It should be noted that passing strings or
any other value outside of ``None``, ``True``, ``False``, ``1``, ``0`` to
the :class:`.Boolean` datatype is **not supported** and version 1.2 will
raise an error for this scenario (or possibly just emit a warning, TBD).
See also :ticket:`4102`.
:ticket:`3730`
.. _change_2837: