Ultimately you have to modify the reflected tables or rewrite them using data
types that are appropriate to the target database. Reflection is in fact
going to produce the most specific type possible, so in this case you're
actually getting sqlalchemy.dialects.mysql.VARCHAR objects and such ba
I'm trying to build a MySQL->PostgreSQL migration tool that reflects tables
from MySQL, then creates them in pg.
So far so good, except that when SQLAlchemy reflects a MySQL table with a
DATETIME column, it reflects it as a sqlalchemy.types.DATETIME, then tries
to create a DATETIME in PostgreSQL.
