Thanks to SQLAlchemy 1.4, Alembic now knows how to handle identities (see
sqlalchemy/alembic#730).
For unknown reasons, identities are now detected as server default values for
the Event table, and are put in database migrations. Explicitely setting the
default value fixes the new alembic migrations, at least for tests.
This is just a placeholder
After sqlalchemy/sqlalchemy#5527 is done support for identity columns should be added to alembic
The text was updated successfully, but these errors were encountered: