Skip to content
Snippets Groups Projects
Commit d4170df4 authored by Kevin Harwell's avatar Kevin Harwell
Browse files

alembic/sqlalchemy: auto increment only allowed on a single column

The extensions table defined two columns (id and priority) as primary key
autoincrement columns. However only one is allowed when defining the primary
key.

This patch removes the autoincrement attribute from the priority column since
it does not need to be as such and really should not have been on there in the
first place.

This patch also removes 'context', 'exten', and 'priority' from the primary key
index and creates a new combined unique contraint index on them.

ASTERISK-26183 #close

Change-Id: Ib9c712c612a4d7ec1edb0dcb77f1bae0905a470b
parent 9042ad40
No related branches found
No related tags found
No related merge requests found
......@@ -31,20 +31,18 @@ down_revision = '43956d550a44'
from alembic import op
import sqlalchemy as sa
def upgrade():
op.create_table(
'extensions',
sa.Column('id', sa.BigInteger, primary_key=True, nullable=False,
unique=True, autoincrement=True),
sa.Column('context', sa.String(40), primary_key=True, nullable=False),
sa.Column('exten', sa.String(40), primary_key=True, nullable=False),
sa.Column('priority', sa.Integer, primary_key=True, nullable=False,
autoincrement=True),
sa.Column('context', sa.String(40), nullable=False),
sa.Column('exten', sa.String(40), nullable=False),
sa.Column('priority', sa.Integer, nullable=False),
sa.Column('app', sa.String(40), nullable=False),
sa.Column('appdata', sa.String(256), nullable=False),
sa.UniqueConstraint('context', 'exten', 'priority')
)
def downgrade():
op.drop_table('extensions')
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment