[Question] How to add a unique index to definition for PGMaterializedView about alembic_utils HOT 4 OPEN

ok found a hook named process_revision_directives, looks like I can customize autogenerated ops. thanks :)

from alembic_utils.

currently there is no way to have alembic_utils manage an index on a materialized view

there is some more discussion and a partial implementation over at #46 but for now I'd recommend managing them manually

If you're trying to do something highly consistent, like add a unique index on id to support concurrent refreshes, you could consider adding a hook in env.py to raise an exception if it detects a materialized view with an id column that does not have an associated unique index. If that sounds useful but you're not sure how to do it, lmk and I'll pull a code sample together

from alembic_utils.

@olirice I would appreciate if you provided a hook example, which can be used with revision --autogenerate. I found a way to make a comparison in env.py, but don't know how to raise an exception after new revision is generated.

from alembic_utils.

Found a way around this by creating a new PGMaterializedViewExtended class which took the indexes that should be included with the MV as a parameter. It then injects create scripts for the indexes into the MV definition to aid with detecting changes. from_database then just pulls the MV, and any indexes relating to the MV and re-creates the definition with both the MV and its indexes. Works nicely on upgrade/downgrade and detects any changes to indexes I've added, remove or changed.

from alembic_utils.