Mike Bayer c63658973c Disallow all ambiguous boolean values for Boolean ...

In release 1.1, the :class:`.Boolean` type was broken in that
boolean coercion via ``bool()`` would occur for backends that did not
feature "native boolean", but would not occur for native boolean backends,
meaning the string ``"0"`` now behaved inconsistently. After a poll, a
consensus was reached that non-boolean values should be raising an error,
especially in the ambiguous case of string ``"0"``; so the :class:`.Boolean`
datatype will now raise ``ValueError`` if an incoming value is not
within the range ``None, True, False, 1, 0``.

Change-Id: If70c4f79c266f0dd1a0306c0ffe7acb9c66c4cc3
Fixes: #4102

2017-10-12 13:39:06 -04:00

..

__init__.py

reorganized unit tests into subdirectories

2006-06-05 17:25:51 +00:00

test_bind.py

Make all tests to be PEP8 compliant

2017-02-07 11:21:56 -05:00

test_ddlevents.py

Make all tests to be PEP8 compliant

2017-02-07 11:21:56 -05:00

test_execute.py

Add SQL Server CI coverage

2017-08-31 17:20:26 -04:00

test_logging.py

Make all tests to be PEP8 compliant

2017-02-07 11:21:56 -05:00

test_parseconnect.py

Make all tests to be PEP8 compliant

2017-02-07 11:21:56 -05:00

test_pool.py

- keep trying to identify the race here. can reproduce locally

2017-04-27 17:44:29 -04:00

test_processors.py

Disallow all ambiguous boolean values for Boolean

2017-10-12 13:39:06 -04:00

test_reconnect.py

First level repair for cx_Oracle 6.0 test regressions

2017-08-18 13:04:14 -04:00

test_reflection.py

Add SQL Server TIMESTAMP / ROWVERSION datatypes

2017-10-04 09:27:31 -04:00

test_transaction.py

Make all tests to be PEP8 compliant

2017-02-07 11:21:56 -05:00