I would definitely agree using postgres in both dev and prod is the way
to go here; sqlite behaves sufficiently differently, particularly around
DDL.
At Axial we previously had multiple databases in concurrent use, with
migrations operating on both databases at once. We modified env.py's
I suspect that this has been asked before in various ways, and perhaps
there's a way of making the documentation section on "multiple databases"
clearer, but my question is:
Can I use the same migration scripts for multiple database engines, or do I
need entirely separate alembic folders to