asterisk/contrib/ast-db-manage/config/versions/1d50859ed02e_create_accountcode.py

"""create accountcode

Revision ID: 1d50859ed02e
Revises: 51f8cb66540e
Create Date: 2014-07-07 21:07:01.661783

"""

# revision identifiers, used by Alembic.
revision = '1d50859ed02e'
down_revision = '51f8cb66540e'

from alembic import op
import sqlalchemy as sa

def upgrade():
    op.add_column('ps_endpoints', sa.Column('accountcode', sa.String(20)))

def downgrade():
    with op.batch_alter_table('ps_endpoints') as batch_op:
        batch_op.drop_column('accountcode')
res_pjsip: Support setting a default accountcode on endpoints Most channel drivers let you specify a default accountcode to be set on channels associated with a particular peer/endpoint/object. Prior to this patch, chan_pjsip/res_pjsip did not support such a setting. This patch adds a new setting to the res_pjsip endpoint object, 'accountcode'. When a channel is created that is associated with an endpoint with this value set, the channel will automatically have its accountcode property set to the value configured for the endpoint. Review: https://reviewboard.asterisk.org/r/3724/ ASTERISK-24000 #close Reported by: Matt Jordan ........ Merged revisions 418756 from http://svn.asterisk.org/svn/asterisk/branches/12 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418757 65c4cc65-6c06-0410-ace0-fbb531ad65f3 2014-07-16 14:03:51 +00:00			`"""create accountcode`

			`Revision ID: 1d50859ed02e`
			`Revises: 51f8cb66540e`
			`Create Date: 2014-07-07 21:07:01.661783`

			`"""`

			`# revision identifiers, used by Alembic.`
			`revision = '1d50859ed02e'`
			`down_revision = '51f8cb66540e'`

			`from alembic import op`
			`import sqlalchemy as sa`

			`def upgrade():`
			`op.add_column('ps_endpoints', sa.Column('accountcode', sa.String(20)))`

			`def downgrade():`
alembic: Fix downgrade and tweak for sqlite Downgrade had a few issues. First there was an errant 'update' statement in add_auto_dtmf_mode that looks like it was a copy/paste error. Second, we weren't cleaning up the ENUMs so subsequent upgrades on postgres failed because the types already existed. For sqlite... sqlite doesn't support ALTER or DROP COLUMN directly. Fortunately alembic batch_operations takes care of this for us if we use it so the alter and drops were converted to use batch operations. Here's an example downgrade: with op.batch_alter_table('ps_endpoints') as batch_op: batch_op.drop_column('tos_audio') batch_op.drop_column('tos_video') batch_op.add_column(sa.Column('tos_audio', yesno_values)) batch_op.add_column(sa.Column('tos_video', yesno_values)) batch_op.drop_column('cos_audio') batch_op.drop_column('cos_video') batch_op.add_column(sa.Column('cos_audio', yesno_values)) batch_op.add_column(sa.Column('cos_video', yesno_values)) with op.batch_alter_table('ps_transports') as batch_op: batch_op.drop_column('tos') batch_op.add_column(sa.Column('tos', yesno_values)) # Can't cast integers to YESNO_VALUES, so dropping and adding is required batch_op.drop_column('cos') batch_op.add_column(sa.Column('cos', yesno_values)) Upgrades from base to head and downgrades from head to base were tested repeatedly for postgresql, mysql/mariadb, and sqlite3. Change-Id: I862b0739eb3fd45ec3412dcc13c2340e1b7baef8 2016-03-01 19:03:04 -07:00			`with op.batch_alter_table('ps_endpoints') as batch_op:`
			`batch_op.drop_column('accountcode')`