alembic_utils
alembic_utils copied to clipboard
An alembic/sqlalchemy extension for migrating sql views, functions, triggers, and policies
When generating a migration for a view that depends on a _new_ *table*, alembic_utils triggers a Postgres error as the dependency doesn't exist yet. This is caused by the code...
Hi there I have a materialized view defined using `PGMaterializedView` in a views.py file. The views had already been created in the database. I want to now add a unique...
Alembic version: 1.7.7 Alembic_utils version: 0.7.7 db: postgres 12 Here's a basic setup: ```sql -- pretend I have SQLAlchemy classes set up to create these CREATE TABLE A ( id...
All ReplaceableEntities that are defined in `env.py` are added on every auto generated migration. Even if there are no change in those entities. Maybe add some sort of checksum? Anyway,...
Fix typo in `PGTrigger.from_sql` docstring * [x] #83
Move all the things to pyproject.toml
As title suggest, these seems to be a bug when creating trigger on a table that doesn't exist yet and is part of the same migration. In such case autogenerated...
I had problems using this to create materialized views with indizes cause of alembic migration tried to replace the views without indizes every time a new autogenerate has to be...
Hello @olirice! I am back with another issue. For my use case, I wanted to be able to manage schemas through alembic as well as all of the views, functions...