From 1bf37888dd245c85e203b2e11c27269fa3dfd7ef Mon Sep 17 00:00:00 2001 From: Chris Hill-Scott Date: Tue, 6 Sep 2016 12:53:57 +0100 Subject: [PATCH] Fix mis-matched database migrations MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The cancelled job migration originally went in as version `0051`. But `0051_set_job_status` went in first in e3fa8bffd7dd436a9d3da68058528d3ad1cd2c09 This meant that Alembic couldn’t work out what order to run the migrations in, and blew up. This commit puts the scheduled job migration after all others. --- ...ncelled_job_status.py => 0053_cancelled_job_status.py} | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) rename migrations/versions/{0051_cancelled_job_status.py => 0053_cancelled_job_status.py} (75%) diff --git a/migrations/versions/0051_cancelled_job_status.py b/migrations/versions/0053_cancelled_job_status.py similarity index 75% rename from migrations/versions/0051_cancelled_job_status.py rename to migrations/versions/0053_cancelled_job_status.py index 902da29ac..6cc5365df 100644 --- a/migrations/versions/0051_cancelled_job_status.py +++ b/migrations/versions/0053_cancelled_job_status.py @@ -1,14 +1,14 @@ """empty message -Revision ID: 0051_cancelled_job_status -Revises: 0050_index_for_stats +Revision ID: 0053_cancelled_job_status +Revises: 0052_drop_jobs_status Create Date: 2016-09-01 14:34:06.839381 """ # revision identifiers, used by Alembic. -revision = '0051_cancelled_job_status' -down_revision = '0050_index_for_stats' +revision = '0053_cancelled_job_status' +down_revision = '0052_drop_jobs_status' from alembic import op import sqlalchemy as sa