92db7569de
Accepting request 1267106 from devel:languages:python
Ana Guerrero2025-04-07 15:35:06 +00:00
178a1bb78f
- Update to 1.15.2 * Fixed issue where the "modified_name" of :class:.AlterColumnOp would not be considered when rendering op directives for autogenerate. While autogenerate cannot detect changes in column name, this would nonetheless impact approaches that made use of this attribute in rewriter recipes. Pull request courtesy lenvk.
Matej Cepl2025-04-04 10:52:09 +00:00
01476ddcb5
Accepting request 1267097 from home:glaubitz:branches:devel:languages:python
Matej Cepl2025-04-04 10:52:09 +00:00
e4fd8ef792
Accepting request 1255008 from devel:languages:python
Ana Guerrero2025-03-24 12:25:16 +00:00
cd60553691
Accepting request 1255008 from devel:languages:python
Ana Guerrero2025-03-24 12:25:16 +00:00
6020932414
- Update to 1.15.1 * Fixed an issue in the new :pep:621 `pyproject.toml layout that prevented Alembic's template files from being included in the .whl` file in the distribution.
Markéta Machová2025-03-21 13:02:23 +00:00
a60e88ef87
Accepting request 1254965 from home:glaubitz:branches:devel:languages:python
Markéta Machová2025-03-21 13:02:23 +00:00
6a1c2d7825
Accepting request 1240751 from devel:languages:python
Ana Guerrero2025-01-29 15:09:48 +00:00
aef9d5867a
Accepting request 1240751 from devel:languages:python
Ana Guerrero2025-01-29 15:09:48 +00:00
c6c000eada
- Update to 1.14.1 * Modified SQLite’s dialect to render “ALTER TABLE <t> RENAME COLUMN” when Operations.alter_column() is used with a straight rename, supporting SQLite’s recently added column rename feature. * Added tzdata to tz extras, which is required on some platforms such as Windows. Pull request courtesy Danipulok. * Fixed bug where autogen render of a “variant” type would fail to catch the variants if the leading type were a dialect-specific type, rather than a generic type.
Markéta Machová2025-01-28 10:11:27 +00:00
0ef0174d3b
Accepting request 1240525 from home:glaubitz:branches:devel:languages:python
Markéta Machová2025-01-28 10:11:27 +00:00
070ff8df28
Accepting request 1225089 from devel:languages:python
Ana Guerrero2024-11-20 15:59:18 +00:00
2567515e67
Accepting request 1225089 from devel:languages:python
Ana Guerrero2024-11-20 15:59:18 +00:00
7d861e46ab
- update to el_1_14_0: * **[usecase] [runtime]** Added a new hook to the DefaultImplDefaultImpl.version_table_impl(). This allows third party dialects to define the exact structure of the alembic_version table, to include use cases where the table requires special directives and/or additional columns so that it may function correctly on a particular backend.
Dirk Mueller2024-11-19 12:32:07 +00:00
139d008e24
- update to el_1_14_0: * **[usecase] [runtime]** Added a new hook to the DefaultImplDefaultImpl.version_table_impl(). This allows third party dialects to define the exact structure of the alembic_version table, to include use cases where the table requires special directives and/or additional columns so that it may function correctly on a particular backend.
Dirk Mueller2024-11-19 12:32:07 +00:00
1758204b1a
Accepting request 1204393 from devel:languages:python
Ana Guerrero2024-09-30 13:34:28 +00:00
62220c50c5
Accepting request 1204393 from devel:languages:python
Ana Guerrero2024-09-30 13:34:28 +00:00
5a2f0ae1c0
- update to 1.13.3: * Render if_exists and if_not_exists parameters in CreateTableOp, CreateIndexOp, DropTableOp and DropIndexOp in an autogenerate context. * Enhance version_locations parsing to handle paths containing newlines. * Added support for Operations.create_table.if_not_exists and Operations.drop_table.if_exists, adding similar functionality to render IF [NOT] EXISTS for table operations in a similar way as with indexes. - update to 1.13.2:
Dirk Mueller2024-09-28 19:20:47 +00:00
c98a287d2d
- update to 1.13.3: * Render if_exists and if_not_exists parameters in CreateTableOp, CreateIndexOp, DropTableOp and DropIndexOp in an autogenerate context. * Enhance version_locations parsing to handle paths containing newlines. * Added support for Operations.create_table.if_not_exists and Operations.drop_table.if_exists, adding similar functionality to render IF [NOT] EXISTS for table operations in a similar way as with indexes. - update to 1.13.2:
Dirk Mueller2024-09-28 19:20:47 +00:00
151458f6b5
Accepting request 1197961 from home:yeey:branches:devel:languages:python
Dirk Mueller2024-08-31 12:30:43 +00:00
7cef7ae656
Accepting request 1197961 from home:yeey:branches:devel:languages:python
Dirk Mueller2024-08-31 12:30:43 +00:00
6c014dee6d
Accepting request 1175384 from devel:languages:python
Ana Guerrero2024-05-21 16:34:38 +00:00
8113455b88
Accepting request 1175384 from devel:languages:python
Ana Guerrero2024-05-21 16:34:38 +00:00
0b3663ef98
Accepting request 1174864 from home:mcalabkova:branches:devel:languages:python:pytest
Matej Cepl2024-05-20 18:21:40 +00:00
f66d6c2f5f
Accepting request 1174864 from home:mcalabkova:branches:devel:languages:python:pytest
Matej Cepl2024-05-20 18:21:40 +00:00
48db8f25d5
Accepting request 1135249 from devel:languages:python
Ana Guerrero2023-12-28 21:54:29 +00:00
23633ebdd6
Accepting request 1135249 from devel:languages:python
Ana Guerrero2023-12-28 21:54:29 +00:00
0602180fd7
- update to 1.13.1: * Fixed :class:.Rewriter so that more than two instances could be chained together correctly, also allowing multiple `process_revision_directives callables to be chained. * Fixed issue where the method :meth:.EnvironmentContext.get_x_argument using the :paramref:.EnvironmentContext.get_x_argument.as_dictionary parameter would fail if an argument key were passed on the command line as a name alone, that is, without an equal sign = or a value. Behavior is repaired where this condition is detected and will return a blank string for the given key, consistent with the behavior where the = sign is present and no value. * Fixed issue where the "unique" flag of an Index` would not be maintained when generating downgrade migrations. * Fixed bug in versioning model where a downgrade across a revision with two down revisions with one down revision depending on the other, would produce an erroneous state in the alembic_version table, making upgrades impossible without manually repairing the table. * Updated pep-484 typing to pass mypy "strict" mode, however including per-module qualifications for specific typing elements not yet complete. * This allows us to catch specific typing issues that have been ongoing such as import symbols not properly exported.
Dirk Mueller2023-12-27 09:37:37 +00:00
0dc16b1301
- update to 1.13.1: * Fixed :class:.Rewriter so that more than two instances could be chained together correctly, also allowing multiple `process_revision_directives callables to be chained. * Fixed issue where the method :meth:.EnvironmentContext.get_x_argument using the :paramref:.EnvironmentContext.get_x_argument.as_dictionary parameter would fail if an argument key were passed on the command line as a name alone, that is, without an equal sign = or a value. Behavior is repaired where this condition is detected and will return a blank string for the given key, consistent with the behavior where the = sign is present and no value. * Fixed issue where the "unique" flag of an Index` would not be maintained when generating downgrade migrations. * Fixed bug in versioning model where a downgrade across a revision with two down revisions with one down revision depending on the other, would produce an erroneous state in the alembic_version table, making upgrades impossible without manually repairing the table. * Updated pep-484 typing to pass mypy "strict" mode, however including per-module qualifications for specific typing elements not yet complete. * This allows us to catch specific typing issues that have been ongoing such as import symbols not properly exported.
Dirk Mueller2023-12-27 09:37:37 +00:00
8967288842
Accepting request 1133430 from devel:languages:python
Ana Guerrero2023-12-15 20:46:38 +00:00
2f30641e2e
Accepting request 1133430 from devel:languages:python
Ana Guerrero2023-12-15 20:46:38 +00:00
dc38f212c2
function correctly with upgrade structures that have multiple, top-level elements, as are generated from the "multi-env" environment template. `if_exists and if_not_exists on index operations also on SQLAlchemy 1.4 series. Previously this feature was mistakenly requiring the 2.0 series. zoneinfo. drop_table_comment()` rendering in a batch table modify would include the "table" and "schema" arguments, which are not accepted in batch as these are already part of the top level block. feature. The compare now correctly accommodates casts and differences in spacing. expression, skipping the compare of these expressions. the indexes and unique constraints was moved to the dialect implementation, allowing greater flexibility.
Dirk Mueller2023-12-15 12:24:07 +00:00
ba00263d8d
function correctly with upgrade structures that have multiple, top-level elements, as are generated from the "multi-env" environment template. `if_exists and if_not_exists on index operations also on SQLAlchemy 1.4 series. Previously this feature was mistakenly requiring the 2.0 series. zoneinfo. drop_table_comment()` rendering in a batch table modify would include the "table" and "schema" arguments, which are not accepted in batch as these are already part of the top level block. feature. The compare now correctly accommodates casts and differences in spacing. expression, skipping the compare of these expressions. the indexes and unique constraints was moved to the dialect implementation, allowing greater flexibility.
Dirk Mueller2023-12-15 12:24:07 +00:00
0bdc71b604
Accepting request 1133130 from home:pgajdos:python
Markéta Machová2023-12-15 12:18:53 +00:00
80ee567113
Accepting request 1133130 from home:pgajdos:python
Markéta Machová2023-12-15 12:18:53 +00:00
2b32ec9ded
Accepting request 1125874 from devel:languages:python
Ana Guerrero2023-11-15 20:06:42 +00:00
f30a7d8070
Accepting request 1125874 from devel:languages:python
Ana Guerrero2023-11-15 20:06:42 +00:00
1856070e91
- update to 1.12.1: * Fixed regression caused by 🎫879 released in 1.7.0 where the ".info" dictionary of `Table would not render in autogenerate create table statements. This can be useful for custom create table DDL rendering schemes so it is restored. * Improved typing in the :paramref:.EnvironmentContext.configure.process_revision_dir ectives callable to better indicate that the passed-in type is :class:.MigrationScript, not the :class:.MigrationOperation base class, and added typing to the example at :ref:cookbook_no_empty_migrations to illustrate. * Repaired :class:.ExecuteSQLOp so that it can participate in "diff" operations; while this object is typically not present in a reflected operation stream, custom hooks may be adding this construct where it needs to have the correct to_diff_tuple() method. * Improved the op.execute() method to correctly accept the * Executable type that is the same which is used in SQLAlchemy Connection.execute(). * Improve typing of the revision parameter in various command functions. * Fixed autogen render issue where expressions inside of indexes for PG need to be double-parenthesized, meaning a single parens must be present within the generated text()` construct. * Alembic now accommodates for Sequence and Identity that support dialect kwargs. This is a change that will be added to SQLAlchemy v2.1. not use semver, nor does its parent project SQLAlchemy;
Dirk Mueller2023-11-14 12:42:00 +00:00
b944f91ecd
- update to 1.12.1: * Fixed regression caused by 🎫879 released in 1.7.0 where the ".info" dictionary of `Table would not render in autogenerate create table statements. This can be useful for custom create table DDL rendering schemes so it is restored. * Improved typing in the :paramref:.EnvironmentContext.configure.process_revision_dir ectives callable to better indicate that the passed-in type is :class:.MigrationScript, not the :class:.MigrationOperation base class, and added typing to the example at :ref:cookbook_no_empty_migrations to illustrate. * Repaired :class:.ExecuteSQLOp so that it can participate in "diff" operations; while this object is typically not present in a reflected operation stream, custom hooks may be adding this construct where it needs to have the correct to_diff_tuple() method. * Improved the op.execute() method to correctly accept the * Executable type that is the same which is used in SQLAlchemy Connection.execute(). * Improve typing of the revision parameter in various command functions. * Fixed autogen render issue where expressions inside of indexes for PG need to be double-parenthesized, meaning a single parens must be present within the generated text()` construct. * Alembic now accommodates for Sequence and Identity that support dialect kwargs. This is a change that will be added to SQLAlchemy v2.1. not use semver, nor does its parent project SQLAlchemy;
Dirk Mueller2023-11-14 12:42:00 +00:00
f8c61da28b
- update to 1.11.2: * Added typing to the default script mako templates. * Added support in autogenerate for NULLS NOT DISTINCT in * the PostgreSQL dialect. * Fixed format string logged when running a post write hook * Added parameters if_exists and if_not_exists for index operations.
Dirk Mueller2023-08-13 19:32:51 +00:00
382fd9b403
- update to 1.11.2: * Added typing to the default script mako templates. * Added support in autogenerate for NULLS NOT DISTINCT in * the PostgreSQL dialect. * Fixed format string logged when running a post write hook * Added parameters if_exists and if_not_exists for index operations.
Dirk Mueller2023-08-13 19:32:51 +00:00
8e2cbab40b
- update to 1.11.1: * As Alembic 1.11.0 is considered a major release (Alembic does not use semver, nor does its parent project SQLAlchemy; this has been clarified <versioning_scheme> in the documentation), * 🎫1130 modified calling signatures for most operations to consider all optional keyword parameters to be keyword-only arguments, to match what was always documented and generated by autogenerate. However, two of these changes were identified as possibly problematic without a more formal deprecation warning being emitted which were the `table_name parameter to :meth:.Operations.drop_index, which was generated positionally by autogenerate prior to version 0.6.3 released in 2014, and type_ in :meth:.Operations.drop_constraint and :meth:.BatchOperations.drop_constraint, which was documented positionally in one example in the batch documentation. * Fixed typing use of :class:~sqlalchemy.schema.Column and other generic SQLAlchemy classes. * Restored the output type of :meth:.Config.get_section to include Dict[str, str] as a potential return type, which had been changed to immutable Mapping[str, str]. When a section is returned and the default is not used, a mutable dictionary is returned. * Added placeholder classes for :class:~.sqla.Computed and * :class:~.sqla.Identity when older 1.x SQLAlchemy versions are in use, namely prior to SQLAlchemy 1.3.11 when the :class:~.sqla.Computed construct was introduced. Previously these were set to None, however this could cause issues with certain codepaths that were using isinstance()` such as one within "batch mode".
Dirk Mueller2023-07-29 21:25:10 +00:00
a898bd0155
- update to 1.11.1: * As Alembic 1.11.0 is considered a major release (Alembic does not use semver, nor does its parent project SQLAlchemy; this has been clarified <versioning_scheme> in the documentation), * 🎫1130 modified calling signatures for most operations to consider all optional keyword parameters to be keyword-only arguments, to match what was always documented and generated by autogenerate. However, two of these changes were identified as possibly problematic without a more formal deprecation warning being emitted which were the `table_name parameter to :meth:.Operations.drop_index, which was generated positionally by autogenerate prior to version 0.6.3 released in 2014, and type_ in :meth:.Operations.drop_constraint and :meth:.BatchOperations.drop_constraint, which was documented positionally in one example in the batch documentation. * Fixed typing use of :class:~sqlalchemy.schema.Column and other generic SQLAlchemy classes. * Restored the output type of :meth:.Config.get_section to include Dict[str, str] as a potential return type, which had been changed to immutable Mapping[str, str]. When a section is returned and the default is not used, a mutable dictionary is returned. * Added placeholder classes for :class:~.sqla.Computed and * :class:~.sqla.Identity when older 1.x SQLAlchemy versions are in use, namely prior to SQLAlchemy 1.3.11 when the :class:~.sqla.Computed construct was introduced. Previously these were set to None, however this could cause issues with certain codepaths that were using isinstance()` such as one within "batch mode".
Dirk Mueller2023-07-29 21:25:10 +00:00
1b1933f9a8
- update to 1.10.4: * Added support for autogenerate comparison of indexes on PostgreSQL which include SQL sort option, such as `ASC or NULLS FIRST. * Fixed various typing issues observed with pyright, including issues involving the combination of :class:.Function and :meth:.MigrationContext.begin_transaction. * Fixed error raised by alembic when running autogenerate after removing a function based index. * Fixed regression where Alembic would not run with older SQLAlchemy 1.3 versions prior to 1.3.24 due to a missing symbol. Workarounds have been applied for older 1.3 versions. * Fixed issue regarding PostgreSQL :class:.ExcludeConstraint, where constraint elements which made use of :func:.literal_column could not be rendered for autogenerate. Additionally, using SQLAlchemy 2.0.5 or greater, :func:.text() constructs are also supported within PostgreSQL :class:.ExcludeConstraint objects for autogenerate render. * Fixed issue in index detection where autogenerate change detection would consider indexes with the same columns but with different order as equal, while in general they are not equivalent in how a database will use them. * Recursive traversal of revision files in a particular revision directory is now supported, by indicating recursive_version_locations = true` in alembic.ini. * Fixed issue where indexes on SQLite which include SQL expressions would not compare correctly, generating false positives under autogenerate. These indexes are now skipped, generating a warning, in the same way that expression-based indexes on PostgreSQL are skipped and
Dirk Mueller2023-05-05 22:20:37 +00:00
092b03ac14
- update to 1.10.4: * Added support for autogenerate comparison of indexes on PostgreSQL which include SQL sort option, such as `ASC or NULLS FIRST. * Fixed various typing issues observed with pyright, including issues involving the combination of :class:.Function and :meth:.MigrationContext.begin_transaction. * Fixed error raised by alembic when running autogenerate after removing a function based index. * Fixed regression where Alembic would not run with older SQLAlchemy 1.3 versions prior to 1.3.24 due to a missing symbol. Workarounds have been applied for older 1.3 versions. * Fixed issue regarding PostgreSQL :class:.ExcludeConstraint, where constraint elements which made use of :func:.literal_column could not be rendered for autogenerate. Additionally, using SQLAlchemy 2.0.5 or greater, :func:.text() constructs are also supported within PostgreSQL :class:.ExcludeConstraint objects for autogenerate render. * Fixed issue in index detection where autogenerate change detection would consider indexes with the same columns but with different order as equal, while in general they are not equivalent in how a database will use them. * Recursive traversal of revision files in a particular revision directory is now supported, by indicating recursive_version_locations = true` in alembic.ini. * Fixed issue where indexes on SQLite which include SQL expressions would not compare correctly, generating false positives under autogenerate. These indexes are now skipped, generating a warning, in the same way that expression-based indexes on PostgreSQL are skipped and
Dirk Mueller2023-05-05 22:20:37 +00:00
54e5ab24a2
- update to 1.9.3: * Fixed issue where rendering of user-defined types that then went onto use the .with_variant() method would fail to render, if using SQLAlchemy 2.0's version of variants.
Dirk Mueller2023-02-10 12:37:16 +00:00
2c273688aa
- update to 1.9.3: * Fixed issue where rendering of user-defined types that then went onto use the .with_variant() method would fail to render, if using SQLAlchemy 2.0's version of variants.
Dirk Mueller2023-02-10 12:37:16 +00:00
8177a78286
- update to 1.9.2: * Fixed typing definitions for :meth:.EnvironmentContext.get_x_argument. Typing stubs are now generated for overloaded proxied methods such as * Fixed regression caused by 🎫1145 where the string transformations applied to server defaults caused expressions such as `(getdate())` to no longer compare as equivalent on SQL Server, others.
Dirk Mueller2023-01-28 14:31:50 +00:00
e0d49627d4
- update to 1.9.2: * Fixed typing definitions for :meth:.EnvironmentContext.get_x_argument. Typing stubs are now generated for overloaded proxied methods such as * Fixed regression caused by 🎫1145 where the string transformations applied to server defaults caused expressions such as `(getdate())` to no longer compare as equivalent on SQL Server, others.
Dirk Mueller2023-01-28 14:31:50 +00:00
9e76909512
- update to 1.9.1: .. change:: 🎟️ 1145 Fixed issue where server default compare would not work for string defaults that contained backslashes, due to mis-rendering of these values when comparing their contents. .. change:: :tags: bug, oracle Implemented basic server default comparison for the Oracle backend; previously, Oracle's formatting of reflected defaults prevented any matches from occurring. .. change:: :tags: bug, sqlite Adjusted SQLite's compare server default implementation to better handle defaults with or without parens around them, from both the reflected and the local metadata side. .. change:: :tags: bug, mssql Adjusted SQL Server's compare server default implementation to better handle defaults with or without parens around them, from both the reflected and the local metadata side.
Dirk Mueller2023-01-05 20:35:40 +00:00
e9b1862555
- update to 1.9.1: .. change:: 🎟️ 1145 Fixed issue where server default compare would not work for string defaults that contained backslashes, due to mis-rendering of these values when comparing their contents. .. change:: :tags: bug, oracle Implemented basic server default comparison for the Oracle backend; previously, Oracle's formatting of reflected defaults prevented any matches from occurring. .. change:: :tags: bug, sqlite Adjusted SQLite's compare server default implementation to better handle defaults with or without parens around them, from both the reflected and the local metadata side. .. change:: :tags: bug, mssql Adjusted SQL Server's compare server default implementation to better handle defaults with or without parens around them, from both the reflected and the local metadata side.
Dirk Mueller2023-01-05 20:35:40 +00:00
a04516353e
Accepting request 1056256 from home:yarunachalam:branches:devel:languages:python
Markéta Machová2023-01-05 19:13:45 +00:00
177e638976
Accepting request 1056256 from home:yarunachalam:branches:devel:languages:python
Markéta Machová2023-01-05 19:13:45 +00:00
7330b420a7
- update to 1.8.1: * Fixed bug where the SQLite implementation of :meth:.Operations.rename_table would render an explicit schema name for both the old and new table name, which while is the standard ALTER syntax, is not accepted by SQLite's syntax which doesn't support a rename across schemas. In particular, the syntax issue would prevent batch mode from working for SQLite databases that made use of attached databases (which are treated as "schemas" in SQLAlchemy). * Added an error raise for the condition where :meth:.Operations.batch_alter_table is used in `--sql mode, where the operation requires table reflection, as is the case when running against SQLite without giving it a fixed Table object. Previously the operation would fail with an internal error. To get a "move and copy" batch operation as a SQL script without connecting to a database, a Table object should be passed to the :paramref:.Operations.batch_alter_table.copy_from` parameter so that reflection may be skipped.
Dirk Mueller2022-08-01 21:39:51 +00:00
cc0a9fabd9
- update to 1.8.1: * Fixed bug where the SQLite implementation of :meth:.Operations.rename_table would render an explicit schema name for both the old and new table name, which while is the standard ALTER syntax, is not accepted by SQLite's syntax which doesn't support a rename across schemas. In particular, the syntax issue would prevent batch mode from working for SQLite databases that made use of attached databases (which are treated as "schemas" in SQLAlchemy). * Added an error raise for the condition where :meth:.Operations.batch_alter_table is used in `--sql mode, where the operation requires table reflection, as is the case when running against SQLite without giving it a fixed Table object. Previously the operation would fail with an internal error. To get a "move and copy" batch operation as a SQL script without connecting to a database, a Table object should be passed to the :paramref:.Operations.batch_alter_table.copy_from` parameter so that reflection may be skipped.
Dirk Mueller2022-08-01 21:39:51 +00:00
aa5cf3b673
- update to 1.7.7: * Fixed issue where using :meth:.Operations.create_table in conjunction with a :class:.CheckConstraint that referred to table-bound :class:.Column objects rather than string expressions would be added to the parent table potentially multiple times, resulting in an incorrect DDL sequence. Pull request courtesy Nicolas CANIART. * The `logging.fileConfig() line in env.py templates, which is used to setup Python logging for the migration run, is now conditional on :attr:.Config.config_file_name not being None. Otherwise, the line is skipped as there is no default logging configuration present. * Fixed bug where an :meth:.Operations.alter_column operation would change a "NOT NULL" column to "NULL" by emitting an ALTER COLUMN statement that did not specify "NOT NULL". (In the absence of "NOT NULL" T-SQL was implicitly assuming "NULL"). An :meth:.Operations.alter_column operation that specifies :paramref:.Operations.alter_column.type should also specify include either :paramref:.Operations.alter_column.nullable or :paramref:.Operations.alter_column.existing_nullable` to inform Alembic as to whether the emitted DDL should include "NULL" or "NOT NULL"; a warning is now emitted if this is missing under this scenario.
Dirk Mueller2022-03-26 20:29:40 +00:00
340d3b4bb4
- update to 1.7.7: * Fixed issue where using :meth:.Operations.create_table in conjunction with a :class:.CheckConstraint that referred to table-bound :class:.Column objects rather than string expressions would be added to the parent table potentially multiple times, resulting in an incorrect DDL sequence. Pull request courtesy Nicolas CANIART. * The `logging.fileConfig() line in env.py templates, which is used to setup Python logging for the migration run, is now conditional on :attr:.Config.config_file_name not being None. Otherwise, the line is skipped as there is no default logging configuration present. * Fixed bug where an :meth:.Operations.alter_column operation would change a "NOT NULL" column to "NULL" by emitting an ALTER COLUMN statement that did not specify "NOT NULL". (In the absence of "NOT NULL" T-SQL was implicitly assuming "NULL"). An :meth:.Operations.alter_column operation that specifies :paramref:.Operations.alter_column.type should also specify include either :paramref:.Operations.alter_column.nullable or :paramref:.Operations.alter_column.existing_nullable` to inform Alembic as to whether the emitted DDL should include "NULL" or "NOT NULL"; a warning is now emitted if this is missing under this scenario.
Dirk Mueller2022-03-26 20:29:40 +00:00
Ana Guerrero
Matej Cepl
Daniel Garcia Moreno
Dominique Leuenberger
Markéta Machová
Dirk Mueller