[mixmastamyk]

It sounds great until you need a centralized billing database and then you might want to just stick with postgres rather than run two kinds of database.

Does anyone have ideas on how to solve that? Not to mention complicating migrations. Unfortunately sqlite-based product docs seem to end right before getting to the hard stuff. Or perhaps I missed them.

[robertlagrant]

We use Alembic migrations with SQLite. No complaints.

[graemep]

Does Alembic provide a simple solution to the limitations of SQLite's alter table?

[robertlagrant]

You're right. Sorry. I shouldn't post when I'm tired. This is listed as a limitation in Alembic, from memory.

Edit: I looked[0]. While it is a SQLite limitation, Alembic does seem to have a way to work around it.

[0] https://alembic.sqlalchemy.org/en/latest/batch.html#working-...

[graemep]

I was asking, not correcting you!

Django ORM also uses the same copy and move method but it warns you against doing it on production databases: "same copy and move method but it warns you against doing it on production databases".

That makes me reluctant to use SQLite for a use case it is otherwise well suited to: multi-tenant applications.

Alembic does not have such dire warnings, but still looks problematic with regard to constraints?