forked from pool/python-alembic
- 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.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-alembic?expand=0&rev=132
This commit is contained in:
@@ -1,3 +0,0 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a2d4d90da70b30e70352cd9455e35873a255a31402a438fe24815758d7a0e5e1
|
||||
size 1252636
|
||||
3
alembic-1.8.1.tar.gz
Normal file
3
alembic-1.8.1.tar.gz
Normal file
@@ -0,0 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cd0b5e45b14b706426b833f06369b9a6d5ee03f826ec3238723ce8caaf6e5ffa
|
||||
size 1255927
|
||||
@@ -1,3 +1,24 @@
|
||||
-------------------------------------------------------------------
|
||||
Mon Aug 1 21:38:44 UTC 2022 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
- 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.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Sat Jun 4 20:32:32 UTC 2022 - Arun Persaud <arun@gmx.de>
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
|
||||
%define skip_python2 1
|
||||
Name: python-alembic
|
||||
Version: 1.8.0
|
||||
Version: 1.8.1
|
||||
Release: 0
|
||||
Summary: A database migration tool for SQLAlchemy
|
||||
License: MIT
|
||||
|
||||
Reference in New Issue
Block a user