forked from pool/python-alembic
Accepting request 965089 from devel:languages:python
- 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.
OBS-URL: https://build.opensuse.org/request/show/965089
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-alembic?expand=0&rev=64
This commit is contained in:
@@ -1,3 +0,0 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6c0c05e9768a896d804387e20b299880fe01bc56484246b0dffe8075d6d3d847
|
||||
size 1235649
|
||||
3
alembic-1.7.7.tar.gz
Normal file
3
alembic-1.7.7.tar.gz
Normal file
@@ -0,0 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4961248173ead7ce8a21efb3de378f13b8398e6630fab0eb258dc74a8af24c58
|
||||
size 1247590
|
||||
@@ -1,3 +1,26 @@
|
||||
-------------------------------------------------------------------
|
||||
Sat Mar 26 20:27:41 UTC 2022 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
- 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.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Mon Feb 14 21:37:49 UTC 2022 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
|
||||
%define skip_python2 1
|
||||
Name: python-alembic
|
||||
Version: 1.7.6
|
||||
Version: 1.7.7
|
||||
Release: 0
|
||||
Summary: A database migration tool for SQLAlchemy
|
||||
License: MIT
|
||||
|
||||
Reference in New Issue
Block a user