Open Stack

On Fri, May 15, 2015 at 4:46 AM, Mike Bayer <mbayer at redhat.com> wrote:

>
>
> On 5/14/15 11:58 AM, Doug Hellmann wrote:
>
>>
>> At one point we were exploring having both sqlalchemy-migrate and
>> alembic run, one after the other, so that we only need to create new
>> migrations with alembic and do not need to change any of the existing
>> migrations. Was that idea dropped?
>>
>
> to my knowledge the idea wasn't dropped.   If a project wants to implement
> that using the oslo.db system, that is fine, however from my POV I'd prefer
> to just port the SQLA-migrate files over and drop the migrate dependency
> altogether.  Whether or not a project does the "run both" step as an
> interim step doesn't affect that effort very much.
>
>
Hi Mike

Just a quick question: How would the alembic scripts know where to start
the migration from if the current installation had been up until that
point been using migrate (I believe both alembic and migrate write to a
small table what the current version is, would you look for that?)?

-Angus


>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150515/64c52ff9/attachment.html>