darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2026-01-31 23:26:23 -05:00
Code Issues Packages Projects Releases Wiki Activity

Fix mis-matched database migrations

Browse Source 
The cancelled job migration originally went in as version `0051`.

But `0051_set_job_status` went in first in
e3fa8bffd7

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.
This commit is contained in:
Chris Hill-Scott
2016-09-06 12:53:57 +01:00
parent 9318eec3a5
commit 1bf37888dd
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
migrations/versions/0051_cancelled_job_status.py → migrations/versions/0053_cancelled_job_status.py
View File

@@ -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