]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- The MySQL dialect now renders TIMESTAMP with NULL / NOT NULL in
authorMike Bayer <mike_mp@zzzcomputing.com>
Thu, 5 Feb 2015 21:17:23 +0000 (16:17 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Thu, 5 Feb 2015 21:24:45 +0000 (16:24 -0500)
commit503a40ad7080344f75cf3347197c44b574c60a9c
tree320c14960706d60c08e0b66c0160c007207c976b
parent068f9a1531c8114360d5fcd964c27fe6a21f4679
- The MySQL dialect now renders TIMESTAMP with NULL / NOT NULL in
all cases, so that MySQL 5.6.6 with the
``explicit_defaults_for_timestamp`` flag enabled will
will allow TIMESTAMP to continue to work as expected when
``nullable=False``.  Existing applications are unaffected as
SQLAlchemy has always emitted NULL for a TIMESTAMP column that
is ``nullable=True``.  fixes #3155
doc/build/changelog/changelog_10.rst
doc/build/changelog/migration_10.rst
lib/sqlalchemy/dialects/mysql/base.py
test/dialect/mysql/test_reflection.py
test/dialect/mysql/test_types.py