Mike -
Thanks for the response (and the all work you've put towards SQLalchemy
and Alembic). I've played around with the reflect_args and that didn't
seem to have much affect. When I remove those, the CHECK constraints
become unnamed. Regardless, I'll continue to mess around with it and see
this area of batch migrations is not well developed, has to deal with
some impossible situations due to SQLite's poor design (allowing unnamed
constraints, not to mention that they refuse to implement ALTER), and is
also in flux (as Alembic is relying upon a buggy behavior in SQLAlchemy
I'm sure that I'm missing a subtle point with batch migrations and
naming conventions for SQLite databases, but I can't figure out what I'm
doing wrong. After renaming a table, I'm using a batch migration to
update a foreign key in a child table. However, after recreating the
child table 2
