python-alembic
A database migration tool for SQLAlchemy
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
4
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:seife:Factory/python-alembic && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
alembic-1.8.1.tar.gz | 0001255927 1.2 MB | |
python-alembic.changes | 0000100702 98.3 KB | |
python-alembic.spec | 0000003078 3.01 KB |
Revision 66 (latest revision is 79)
Dominique Leuenberger (dimstar_suse)
accepted
request 992110
from
Dirk Mueller (dirkmueller)
(revision 66)
- 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.
Comments 0