The change in behavior for SQLAlchemy (not dropping the CHECK constraint) still sounds like a regression, but if the work-around was already in our code base then I agree we need to fix it here.
The change in behavior for SQLAlchemy (not dropping the CHECK constraint) still sounds like a regression, but if the work-around was already in our code base then I agree we need to fix it here.