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" > columns simultaneously, the code itself doesn't have to guess because > it's tied to a "version" of the schema that may include only the old, > the old and new, or only the new. > > That is, they have a multi-step versioning approach, if that makes sense.
Interesting. Do you know if this is written up anywhere (the SQLAlchemy-specific parts of it, I mean)? I may be able to work with this approach. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
