I've been using Flask-Migrate (Alembic) for updating my database. I updated my
sqlalchemy.exc.IntegrityError: (_mysql_exceptions.IntegrityError) (1215, 'Cannot add foreign key constraint') [SQL: u'\nCREATE TABLE topics (\n\tid INTEGER NOT NULL AUTO_INCREMENT, \n\t`subjectID` INTEGER, \n\ttopic VARCHAR(150) NOT NULL, \n\tPRIMARY KEY (id), \n\tFOREIGN KEY(`subjectID`) REFERENCES subjects (id)\n)\n\n']
alembic.util.CommandError: Target database is not up to date.
python manage.py db downgrade --sql b877018671c:36949b1cca31
python manage.py db current
Alembic stores the db version in a table it creates called
alembic_version. This table contains a single field and row
alembic_version.version_num. Make sure the value for this matches the filename of the most recent file in
migrations/version. This version number is also contained inside the revision file in the
revision variable that generally shows up on line 26 of the file. Make sure it matches the db version.
Another option is to simply drop the db and recreate it using alembic. If this is a development environment, where the data is not important, that would be my recommendation.