Comment 11 for bug 1908552

It's quite tricky to detect that dbupgrade shouldn't do anything, since views and triggers aren't modeled as db migrations.

Modelling views and triggers as db migrations is tricky in itself, and I'm not even sure it's possible to do that with Django. But what we could do, is to manually create an empty db migration whenever we change a trigger or view. That way, dbupgrade could safely look whether all the migrations are in the db already, and exit without doing anything.

Since this will require a db migration, which is hard to include in minor releases, it would be worth looking into where the code is hanging, and try to do a graceful exit in that case.