Cannot complete Flask-Migration

Question

I've setup a local Postgres DB with SQLAlchemy and cannot commit my first entry. I keep on getting this error...

ProgrammingError: (ProgrammingError) relation "user" does not exist
LINE 1: INSERT INTO "user" (name, email, facebook_id, facebook_token...

It seems like the fields aren't matching to those in the database. I'm trying to migrate using flask-migrate but, when I run $ python app.py db migrate I get this error...

raise util.CommandError("No such revision '%s'" % id_)
alembic.util.CommandError: No such revision '39408d6b248d'

It may be best to delete everything and start from scratch as it seems I have botched my database setup and / or migration but I'm not sure how to.

UPDATE: The database has started working now (I dropped and created it again). However, I'm still getting the same error trying to run migrations and it turns out the "no such revision '39408d6b248d' is referring to a migration from an unrelated project. I re-installed flask-migrate but same error.

Answer 1

It means that the entry in table alembic_version of your db is "39408d6b248d" and there's no migration file related to it in migrations folder (by default migrations/versions).

So better drop the table alembic_version from your db and do

$ python app.py db history to get the new head of migrations, say, 5301c31377f2

Now run $ python app.py db stamp 5301c31377f2 to let alembic know that it's your migration head (which gets stored in table alembic_version).

Answer 2

Assuming that you have checked that the database exists using psql or pgAdmin, this error usually means exactly what it says. That can be due to either:

• not connecting to the correct database instance (check your db url: host/port and db name)
• not correctly configuring SQLAlchemy (see: SQLAlchemy create_all() does not create tables)

Answer 3

Alembic keeps the migration history in your database, this is why it still recognises there is another revision there. I keep my project on Heroku so I was able to just do heroku pg:pull ... to be able to get a new copy of my database. Prior to this you will have to drop your local db. In case you don't want to drop your local, I think dropping the table should work too. I use the PG Commander as a GUI tool to quickly browse my databases.

Answer 4

the first step to do is run this command alembic current you should get an error as mentioned above (the goal is to make sure that this command returns a valid response).

the reason why u're getting this is bc alembic is confused about your current state.. it's assuming that you should be in revision 39408d6b248d but then decides that that revision is invalid.

to investigate this, let's find out which revisions are considered valid by alembic, run this command:

alembic history --verbose

you'll get a list of all previous revisions (note: it's a good idea to attach a message beside each revision.. think about it as a good git commit message)

Rev: 594cc72f56fd (head)
Parent: 262f40e28682
Path: ***************

    adjust context_id in log table so that it is a substring of the object_id

    Revision ID: 594cc72f56fd
    Revises: 262f40e28682
    Create Date: 2015-07-22 14:31:52.424862

Rev: 262f40e28682
Parent: 1dc902bd1c2
Path: ***************

    add context_id column to log table

    Revision ID: 262f40e28682
    Revises: 1dc902bd1c2
    Create Date: 2015-07-22 11:05:37.654553

Rev: 1dc902bd1c2
Parent: <base>
Path: ***************

    Initial database setup

    Revision ID: 1dc902bd1c2
    Revises: 
    Create Date: 2015-07-06 09:55:11.439330

the revision 39408d6b248d clearly doesn't exist in the above revisions. This revision is stored in the alembic_table in the database.. you can verify by going to your dbase and running:

$ select * from alembic_version;
 version_num  
--------------
 57ac999dcaa7

so now you should review the state of your database and see where it fits vis-a-vis the revisions outputted above:

in my case, by poking around my dbase it becomes obvious which revision i'm in right now.. which is that dbase has been setup,, but the other revisions haven't been included yet.

so now i replace the value on the dbase with the one i found from the history command above:

vibereel=> update alembic_version set version_num = '1dc902bd1c2';

and now running alembic current returns

INFO  [alembic.migration] Context impl PostgresqlImpl.
INFO  [alembic.migration] Will assume transactional DDL.
1dc902bd1c2

done.

Answer 5

I ran into a similar issue. After performing the python manage.py db migrate command the database tables were not created, there was only an alembic table in the database.

I found the solution in the flask-migrate documentation: https://flask-migrate.readthedocs.org/en/latest/

The migration script needs to be reviewed and edited, as Alembic currently does not detect every change you make to your models. In particular, Alembic is currently unable to detect indexes. Once finalized, the migration script also needs to be added to version control.

Then you can apply the migration to the database:

python manage.py db upgrade

This command created the tables and applied the database migrations.

Answer 6

I got the same error yesterday, for my case the revision number '39408d6b248d' is due to your previous migration upgrade actions, each time your ran upgrade script then an Alembic version will be generated and stored in data.sqlite.

you must have done any upgrade which generated above '39408d6b248d', but then you deleted whole migrations/ directory and removed all upgrade scripts. The database e.g. data.sqlite still stores '39408d6b248d' but there aren't according migration script exists.

for my solution I delete whole Alembic versions in database and did all upgrades from scratch.

Answer 7

I had the same issue. According to the version in alembic_version table in db, migration action is looking for that version in /migrations/versions folder which has already been deleted. Therefore solution is to delete alembic_version table: If you are using sqlite, 1. Open your xxx.sqlite db file. sqlite3 xxx.sqlite 2. check tables .tables 3. you will see alembic_version, delete it DROP TABLE alembic_version

Answer 8

flask-migrate will create a table named "alembic_version" in your database.
so you should drop this table and delete migrations folder in your project.
and then use $ python app.py db init again...
I think $ python app.py db migrate will work fine.