On 07/06/2016 10:23 PM, Jon Davidson wrote:
On Wed, Jul 6, 2016, at 12:25 PM, Mike Bayer wrote:
so yeah this use case is a big deal now, because all of openstack wants
to do it.
However in openstack, they at least know what version the target schema
is at, so while they need to run code that
On Wed, Jul 6, 2016, at 12:25 PM, Mike Bayer wrote:
> so yeah this use case is a big deal now, because all of openstack wants
> to do it.
>
> However in openstack, they at least know what version the target schema
> is at, so while they need to run code that talks to the "old" and "new"
>
SQLAlchemy release 1.0.14 is now available.
This is the latest release in the 1.0 series which includes a variety of
bug fixes that have accumulated since the last 1.0 release. This release
happens to only feature Core and dialect level changes; none are ORM
specific. All applicable fixes
On 07/06/2016 12:04 AM, Jon Davidson wrote:
In my current employer's setup, we use SQLAlchemy core and ORM, but we
use a homegrown migration system instead of alembic. When possible, we
want to write code so that it can work equally well with the old DB
schema and the new DB schema.
In this
