diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2015-02-05 16:17:23 -0500 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2015-02-05 16:24:45 -0500 |
commit | 503a40ad7080344f75cf3347197c44b574c60a9c (patch) | |
tree | 320c14960706d60c08e0b66c0160c007207c976b /lib/sqlalchemy/ext/associationproxy.py | |
parent | 068f9a1531c8114360d5fcd964c27fe6a21f4679 (diff) | |
download | sqlalchemy-503a40ad7080344f75cf3347197c44b574c60a9c.tar.gz |
- 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
Diffstat (limited to 'lib/sqlalchemy/ext/associationproxy.py')
0 files changed, 0 insertions, 0 deletions