From 52750e74ee03e06c16e176ca7e48284d8660905f Mon Sep 17 00:00:00 2001 From: Charlton Austin Date: Mon, 22 May 2017 09:55:40 -0400 Subject: [PATCH] fix(add notification number): add explicit default there is a possibility that this will not work with postgres Issue: https://www.pivotaltracker.com/story/show/144646649 - [ ] It works! - [ ] Comments provide sufficient explanations for the next contributor - [ ] Tests cover changes and corner cases - [ ] Follows Quay syntax patterns and format --- .../dc4af11a5f90_add_notification_number_of_failures_.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/data/migrations/versions/dc4af11a5f90_add_notification_number_of_failures_.py b/data/migrations/versions/dc4af11a5f90_add_notification_number_of_failures_.py index 363ae7438..ffde9d687 100644 --- a/data/migrations/versions/dc4af11a5f90_add_notification_number_of_failures_.py +++ b/data/migrations/versions/dc4af11a5f90_add_notification_number_of_failures_.py @@ -15,7 +15,10 @@ from alembic import op def upgrade(tables): - op.add_column('repositorynotification', sa.Column('number_of_failures', sa.Integer(), nullable=False)) + op.add_column('repositorynotification', sa.Column('number_of_failures', + sa.Integer(), + nullable=False, + server_default='0')) op.bulk_insert(tables.logentrykind, [ {'name': 'reset_repo_notification'}, ])