Materialized view dependencies for non-breaking migrations

[alainux]

Hello!

I am facing currently a very tedious issue when pgMaterializedView depends on another view, because if I modify the dependency, the migrator script is not aware that it will fail to drop the dependent view first.

The same thing happens when adding multiple views at the same time that may depend on each other, the generated migration is not aware of the order and it fails to execute.

Is there something I am missing?

Thank you

[hunterwilhelm]

I just ran into this issue. I don't think I can use drizzle for this problem. I am going to eject my views and materialized from being generated by drizzle, and instead have a script that copies the new repeatable migration into a custom migration in drizzle.