migrations/versions/0053_cancelled_job_status.py

"""empty message

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 = '0053_cancelled_job_status'
down_revision = '0052_drop_jobs_status'

from alembic import op
import sqlalchemy as sa
from sqlalchemy.dialects import postgresql

def upgrade():
    op.execute("INSERT INTO job_status VALUES ('cancelled')")

def downgrade():
    op.execute("UPDATE jobs SET job_status = 'finished' WHERE job_status = 'cancelled'")
    op.execute("DELETE FROM job_status WHERE name = 'cancelled';")
Add an endpoint to cancel a job If you schedule a job you might change your mind or circumstances might change. So you need to be able to cancel it. This commit adds a `POST` endpoint for individual jobs which sets their status to `cancelled`. This also means adding a new status of `cancelled`, so there’s a migration… 2016-09-01 14:31:01 +01:00			`"""empty message`

Fix mis-matched database migrations 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. 2016-09-06 12:53:57 +01:00			`Revision ID: 0053_cancelled_job_status`
			`Revises: 0052_drop_jobs_status`
Add an endpoint to cancel a job If you schedule a job you might change your mind or circumstances might change. So you need to be able to cancel it. This commit adds a `POST` endpoint for individual jobs which sets their status to `cancelled`. This also means adding a new status of `cancelled`, so there’s a migration… 2016-09-01 14:31:01 +01:00			`Create Date: 2016-09-01 14:34:06.839381`

			`"""`

			`# revision identifiers, used by Alembic.`
Fix mis-matched database migrations 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. 2016-09-06 12:53:57 +01:00			`revision = '0053_cancelled_job_status'`
			`down_revision = '0052_drop_jobs_status'`
Add an endpoint to cancel a job If you schedule a job you might change your mind or circumstances might change. So you need to be able to cancel it. This commit adds a `POST` endpoint for individual jobs which sets their status to `cancelled`. This also means adding a new status of `cancelled`, so there’s a migration… 2016-09-01 14:31:01 +01:00
			`from alembic import op`
			`import sqlalchemy as sa`
			`from sqlalchemy.dialects import postgresql`

			`def upgrade():`
			`op.execute("INSERT INTO job_status VALUES ('cancelled')")`

			`def downgrade():`
			`op.execute("UPDATE jobs SET job_status = 'finished' WHERE job_status = 'cancelled'")`
			`op.execute("DELETE FROM job_status WHERE name = 'cancelled';")`