Hi,
What's the best practice for "tagging" an Alembic revision, that is to
denote e.g. that 1ffbeb5179a5 is the database revision matching version
1.4.0 of the software?
I can do it in documentation, of course, but would prefer a method allowing
e.g. "alembic downgrade v1.2.1".
I guess I could simply rename the revision identifier to "v1.4.0", since
Alembic apparently doesn't strictly enforce that identifiers must be
hexadecimal? That does seem like quite a hack, though, and causes problems
with prefix-matching ("v1.1" could match "v1.12"). It's also not clear
whether it's safe to assume that Alembic will continue to allow arbitrary
strings as revision IDs.
Branch labels does not seem like a good fit for solving the problem either.
Would there be interest in adding a dedicated tagging feature?
Best,
Søren
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy-alembic+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
