<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-openembedded.git/meta-python/recipes-devtools/python/python3-alembic_1.7.6.bb, branch kirkstone-next</title>
<subtitle>Mirror of git.openembedded.org/meta-openembedded</subtitle>
<id>https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=kirkstone-next</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=kirkstone-next'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/'/>
<updated>2022-03-28T12:35:31+00:00</updated>
<entry>
<title>python3-alembic: upgrade 1.7.6 -&gt; 1.7.7</title>
<updated>2022-03-28T12:35:31+00:00</updated>
<author>
<name>Xu Huan</name>
<email>xuhuan.fnst@fujitsu.com</email>
</author>
<published>2022-03-24T09:17:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=bbb42608522d54bbfb53406ecb57d78375c2eb42'/>
<id>urn:sha1:bbb42608522d54bbfb53406ecb57d78375c2eb42</id>
<content type='text'>
changelog:
===============================================================================
-[bug] [operations]

Fixed issue where using Operations.create_table() in conjunction with a
CheckConstraint that referred to table-bound 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.

-[bug] [environment]

The logging.fileConfig() line in env.py templates, which is used to setup Python
logging for the migration run, is now conditional on Config.config_file_name not
being None. Otherwise, the line is skipped as there is no default logging
configuration present.

-[bug] [mssql]

Fixed bug where an 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 Operations.alter_column() operation that specifies
Operations.alter_column.type should also specify include either
Operations.alter_column.nullable or 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.

Signed-off-by: Xu Huan &lt;xuhuan.fnst@fujitsu.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Trevor Gamblin &lt;trevor.gamblin@windriver.com&gt;
</content>
</entry>
<entry>
<title>python3-alembic upgrade 1.7.5 -&gt; 1.7.6</title>
<updated>2022-02-24T16:30:26+00:00</updated>
<author>
<name>Xu Huan</name>
<email>xuhuan.fnst@fujitsu.com</email>
</author>
<published>2022-02-22T09:03:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=87ae20aa982a10ca1a68daf573dbe65db9a12231'/>
<id>urn:sha1:87ae20aa982a10ca1a68daf573dbe65db9a12231</id>
<content type='text'>
License-Update:
year updated to 2022

changelog:
===============================================================================
Add a new command alembic ensure_version, which will ensure that the Alembic
version table is present in the target database, but does not alter its
contents. Pull request courtesy Kai Mueller.

Fixed regression where usage of a with_variant() datatype in conjunction
with the existing_type option of op.alter_column() under batch mode would
lead to an internal exception.

Implemented support for recognizing and rendering SQLAlchemy “variant” types
going forward into SQLAlchemy 2.0, where the architecture of “variant”
datatypes will be changing.

Added a rule to the MySQL impl so that the translation between JSON / LONGTEXT
is accommodated by autogenerate, treating LONGTEXT from the server as
equivalent to an existing JSON in the model.

Signed-off-by: Xu Huan &lt;xuhuan.fnst@fujitsu.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Trevor Gamblin &lt;trevor.gamblin@windriver.com&gt;
</content>
</entry>
</feed>
