]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- Fixed issue where the SQL Server dialect would reflect a string-
authorMike Bayer <mike_mp@zzzcomputing.com>
Thu, 30 Jul 2015 14:34:36 +0000 (10:34 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Thu, 30 Jul 2015 14:34:36 +0000 (10:34 -0400)
commitdd6110eed335154e0ae14b2dba13e44af76c4f2b
tree14090663623b65008e49d5eb5d428003e7ea19f5
parentd8efa2257ec650b345ec6e840984387263a957a6
- Fixed issue where the SQL Server dialect would reflect a string-
or other variable-length column type with unbounded length
by assigning the token ``"max"`` to the
length attribute of the string.   While using the ``"max"`` token
explicitly is supported by the SQL Server dialect, it isn't part
of the normal contract of the base string types, and instead the
length should just be left as None.   The dialect now assigns the
length to None on reflection of the type so that the type behaves
normally in other contexts.
fixes #3504
doc/build/changelog/changelog_11.rst
doc/build/changelog/migration_11.rst
lib/sqlalchemy/dialects/mssql/base.py
test/dialect/mssql/test_reflection.py