<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-openembedded.git/meta-python/recipes-devtools/python/python3-alembic_1.5.3.bb, branch master</title>
<subtitle>Mirror of git.openembedded.org/meta-openembedded</subtitle>
<id>https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/'/>
<updated>2021-02-05T18:26:11+00:00</updated>
<entry>
<title>python3-alembic: Upgrade 1.5.3 -&gt; 1.5.4</title>
<updated>2021-02-05T18:26:11+00:00</updated>
<author>
<name>Leon Anavi</name>
<email>leon.anavi@konsulko.com</email>
</author>
<published>2021-02-04T13:19:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=8ccfa76f8212df3d8d6bd8f398c831cb20590e3d'/>
<id>urn:sha1:8ccfa76f8212df3d8d6bd8f398c831cb20590e3d</id>
<content type='text'>
Upgrade to release 1.5.4:

- Fixed bug in versioning model where a downgrade across a
  revision with a dependency on another branch, yet an ancestor
  is also dependent on that branch, would produce an erroneous
  state in the alembic_version table, making upgrades impossible
  without manually repairing the table.

Signed-off-by: Leon Anavi &lt;leon.anavi@konsulko.com&gt;
Acked-by: Trevor Gamblin &lt;trevor.gamblin@windriver.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>python3-alembic: Upgrade 1.5.2 -&gt; 1.5.3</title>
<updated>2021-02-03T02:50:06+00:00</updated>
<author>
<name>Leon Anavi</name>
<email>leon.anavi@konsulko.com</email>
</author>
<published>2021-02-01T12:45:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=ba316757136f8bc9ea8de80d2d13c1517324376a'/>
<id>urn:sha1:ba316757136f8bc9ea8de80d2d13c1517324376a</id>
<content type='text'>
Upgrade to release 1.5.3:

- Changed the default ordering of “CREATE” and “DROP” statements
  indexes and unique constraints within the autogenerate process,
  so that for example in an upgrade() operation, a particular
  index or constraint that is to be replaced such as for a casing
  convention change will not produce any naming conflicts. For
  foreign key constraint objects, this is already how constraints
  are ordered, and for table objects, users would normally want to
  use Operations.rename_table() in any case.
- Fixed assorted autogenerate issues with SQL Server.
- Fixed issue where autogenerate rendering of op.alter_column()
  would fail to include MySQL existing_nullable=False if the column
  were part of a primary key constraint within the table metadata.

Signed-off-by: Leon Anavi &lt;leon.anavi@konsulko.com&gt;
Acked-by: Trevor Gamblin &lt;trevor.gamblin@windriver.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
</feed>
