From c717b9f699da5a79db1ed00446ed6e9b195280c7 Mon Sep 17 00:00:00 2001 From: Jeff Hodges Date: Fri, 28 Aug 2015 00:56:41 -0700 Subject: [PATCH] disallow all null values in registrations table This prevents weird bad things happening in the future. --- ...150828005159_RegistrationsNotNullManyFields.sql | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 sa/_db/migrations/20150828005159_RegistrationsNotNullManyFields.sql diff --git a/sa/_db/migrations/20150828005159_RegistrationsNotNullManyFields.sql b/sa/_db/migrations/20150828005159_RegistrationsNotNullManyFields.sql new file mode 100644 index 000000000..f3e00a450 --- /dev/null +++ b/sa/_db/migrations/20150828005159_RegistrationsNotNullManyFields.sql @@ -0,0 +1,14 @@ + +-- +goose Up +-- SQL in section 'Up' is executed when this migration is applied + +ALTER TABLE `registrations` MODIFY `contact` varchar(255) NOT NULL; +ALTER TABLE `registrations` MODIFY `agreement` varchar(255) NOT NULL; +ALTER TABLE `registrations` MODIFY `LockCol` bigint(20) NOT NULL; + +-- +goose Down +-- SQL section 'Down' is executed when this migration is rolled back + +ALTER TABLE `registrations` MODIFY `contact` varchar(255) DEFAULT NULL; +ALTER TABLE `registrations` MODIFY `agreement` varchar(255) DEFAULT NULL; +ALTER TABLE `registrations` MODIFY `LockCol` bigint(20) DEFAULT NULL;