3 ms·
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 limitatio
by robertlagrant 3y ago
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-in-offline-mode https://alembic.sqlalchemy.org/en/latest/batch.html#working-...
- graemep 3y agoI 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?