On 07/18/2018 02:07 AM, Sebastian Hagedorn wrote:
I have only now started playing around with Mailman 3.2, because I never managed to get the earlier releases to work, and reading through the documentation I thought that such situations could be handled with Alembic, as described here under "Database Migrations":
<http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html>
Is that not the case, and if not, in what cases can or should it be used?
Alembic is used by Mailman core to migrate changes in Mailman's data models (database schema). It interfaces with SQLAlchemy <https://www.sqlalchemy.org/> which is used by Mailman core to interface with the underlying SQL database. Alembic is used by mailman developers to create migrations when table and column definitions are modified for some reason. It is not used by end users unless they are actually modifying Mailman's code and database schema.
Alembic does not do migrations based on a change in the underlying database engine, e.g. SQLite -> PostgreSQL.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan