to fix this for SQLite, we'd have to manually add UniqueConstraint objects to the reflected table after using inspector.get_unique_constraints(), that is, backport SQLAlchemy 1.0's feature. I'd rather whack this method entirely, so putting it out there to estimate the impact of either approach.
to fix this for SQLite, we'd have to manually add UniqueConstraint objects to the reflected table after using inspector. get_unique_ constraints( ), that is, backport SQLAlchemy 1.0's feature. I'd rather whack this method entirely, so putting it out there to estimate the impact of either approach.