Postgres requires defaults for non-nullable cols, even integer ones
Fixes https://jira.coreos.com/browse/QUAY-912
This commit is contained in:
parent
ecf6db256d
commit
4418772745
1 changed files with 2 additions and 2 deletions
|
@ -16,8 +16,8 @@ from sqlalchemy.dialects import mysql
|
||||||
|
|
||||||
def upgrade(tables):
|
def upgrade(tables):
|
||||||
# ### commands auto generated by Alembic - please adjust! ###
|
# ### commands auto generated by Alembic - please adjust! ###
|
||||||
op.add_column('repositorybuildtrigger', sa.Column('successive_failure_count', sa.Integer(), nullable=False))
|
op.add_column('repositorybuildtrigger', sa.Column('successive_failure_count', sa.Integer(), server_default='0', nullable=False))
|
||||||
op.add_column('repositorybuildtrigger', sa.Column('successive_internal_error_count', sa.Integer(), nullable=False))
|
op.add_column('repositorybuildtrigger', sa.Column('successive_internal_error_count', sa.Integer(), server_default='0', nullable=False))
|
||||||
# ### end Alembic commands ###
|
# ### end Alembic commands ###
|
||||||
|
|
||||||
op.bulk_insert(
|
op.bulk_insert(
|
||||||
|
|
Reference in a new issue