TypeError on create_index and mssql_include #516
Closed
Labels
Comments
Changes by Jimmy Thrasibule (@spack):
|
Jimmy Thrasibule (@spack) wrote: Note that if I go back to alembic 1.0.1 it works. |
Michael Bayer (@zzzeek) wrote: oh, we just added this, OK, then it's a quick regression. |
Michael Bayer (@zzzeek) wrote: |
Michael Bayer (@zzzeek) wrote: Check for mssql_include is None Fixed regression caused by Change-Id: I4c3a9d1f12017b62a7affa3863bba6e2bead67cf → 174cb4b |
Changes by Michael Bayer (@zzzeek):
|
vvvrrooomm
pushed a commit
to vvvrrooomm/alembic
that referenced
this issue
Jan 10, 2019
Fixed regression caused by🎫 `513`, where the logic to consume ``mssql_include`` was not correctly interpreting the case where the flag was not present, breaking the ``op.create_index`` directive for SQL Server as a whole. Change-Id: I4c3a9d1f12017b62a7affa3863bba6e2bead67cf Fixes: sqlalchemy#516
vvvrrooomm
pushed a commit
to vvvrrooomm/alembic
that referenced
this issue
Jan 10, 2019
Fixed regression caused by🎫 `513`, where the logic to consume ``mssql_include`` was not correctly interpreting the case where the flag was not present, breaking the ``op.create_index`` directive for SQL Server as a whole. Change-Id: I4c3a9d1f12017b62a7affa3863bba6e2bead67cf Fixes: sqlalchemy#516
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Migrated issue, originally created by Jimmy Thrasibule (@spack)
Using MSSQL Express 2017 and
pymssql
, aTypeError
is raised during schema upgrade when creating an index.The text was updated successfully, but these errors were encountered: