python/python-alembic
SHA256
15
0
Fork 0
forked from pool/python-alembic
Code Pull Requests Activity

- update to 1.8.1:

Browse Source 
* 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:
Dirk Mueller
2022-08-01 21:39:51 +00:00
committed by Git OBS Bridge
parent ba4310683f
commit 7330b420a7
4 changed files with 25 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
python-alembic.changes
View File

@@ -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>