When comparing Djangos ORM and Flasks SQLAlchemy extension, what is a key difference in how they handle database migrations?

Django ORM includes a built$-$in migration tool, while Flask requires an external extension like Flask$-$Migrate

Flasks SQLAlchemy supports more databases out of the box compared to Djangos ORM

C$)$ Django ORM cannot roll back migrations once applied, unlike Flask SQLAlchemy

Flask SQLAlchemy provides a built$-$in admin interface similar to Djangos admin