On Fri, Apr 20, 2012 at 03:44:55PM -0400, Michael Bayer wrote: > > The one thing that's needed as far as Alembic is concerned is the > ability to control the name of the actual "migration" table per > environment, this is a short feature add that's been sitting as an > enhancement request for some time now.
Since you mention it, I posted patches to https://bitbucket.org/zzzeek/alembic/issue/34/make-version-table-name-configurable awhile ago and was awaiting feedback on them (until I forgot about them.) The patches in addition to supporting a configurable version table name also support two-column version tables which can be shared between Alembic environments. (If you want to veto the two-column version table idea, I can whittle it down to just the configurable-version-table-name part pretty easily.) Cheers, Jeff -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
