diff options
author | zhengruoqin <zhengrq.fnst@fujitsu.com> | 2022-07-22 09:35:12 +0800 |
---|---|---|
committer | Khem Raj <raj.khem@gmail.com> | 2022-07-24 06:28:56 -0700 |
commit | e145b72b42483056ad3e75cc0b954846bcfa8fbc (patch) | |
tree | adfaaefa686ecb18014c4776db364c0e6b5954d2 /meta-python/recipes-devtools/python/python3-blinker/0001-use-pytest-instead-of-deprecated-nose.patch | |
parent | 0c4f3404ef367ff3aa2a28947fc717215c735aa1 (diff) | |
download | meta-openembedded-e145b72b42483056ad3e75cc0b954846bcfa8fbc.tar.gz |
python3-alembic: upgrade 1.8.0 -> 1.8.1
Changelog:
==========
[bug] [sqlite]
--------------
Fixed bug where the SQLite implementation of 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).
[bug] [batch]
-------------
Added an error raise for the condition where 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
Operations.batch_alter_table.copy_from parameter so that reflection may be
skipped.
Signed-off-by: Zheng Ruoqin <zhengrq.fnst@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-blinker/0001-use-pytest-instead-of-deprecated-nose.patch')
0 files changed, 0 insertions, 0 deletions