From 11225b7149f5c777d90d3464c48a9ae59442ca90 Mon Sep 17 00:00:00 2001 From: Chris Hill-Scott Date: Wed, 29 Aug 2018 12:25:57 +0100 Subject: [PATCH] Make branding type non-nullable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit We’ve already removed all the `null` values, and made it impossible to add new brandings with a `null` brand type. Making it a database constraint just gives us extra safety. --- .../versions/0220_email_brand_type_non_null.py | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 migrations/versions/0220_email_brand_type_non_null.py diff --git a/migrations/versions/0220_email_brand_type_non_null.py b/migrations/versions/0220_email_brand_type_non_null.py new file mode 100644 index 000000000..7bc04a4ca --- /dev/null +++ b/migrations/versions/0220_email_brand_type_non_null.py @@ -0,0 +1,17 @@ +""" + Revision ID: 0220_email_brand_type_non_null +Revises: 0219_default_email_branding +Create Date: 2018-08-24 13:36:49.346156 + """ +from alembic import op + +revision = '0220_email_brand_type_non_null' +down_revision = '0219_default_email_branding' + + +def upgrade(): + op.alter_column('email_branding', 'brand_type', nullable=False) + + +def downgrade(): + op.alter_column('email_branding', 'brand_type', nullable=True)