pjsip realtime: already created enum failure for postgresql
authorKevin Harwell <kharwell@digium.com>
Thu, 6 Feb 2014 18:11:34 +0000 (18:11 +0000)
committerKevin Harwell <kharwell@digium.com>
Thu, 6 Feb 2014 18:11:34 +0000 (18:11 +0000)
commit6a1cb65679c367751b331e944234a915845ece30
treecffcd5afb2a59b10e837bec86f8fba29277e7201
parentb5ca213e34055724a5cd669938e356569847edcb
pjsip realtime: already created enum failure for postgresql

If an enum had been previously created the alembic script would attempt to
re-create it and an error would be generated while running migrations for a
postgresql server.  The work around for this is to use the ENUM object type
for postgres as opposed to the generic enum type used by sqlalchemy. Using
this type in the script seems to work properly for both postgres and mysql.
........

Merged revisions 407572 from http://svn.asterisk.org/svn/asterisk/branches/12

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@407574 65c4cc65-6c06-0410-ace0-fbb531ad65f3
contrib/ast-db-manage/config/versions/2fc7930b41b3_add_pjsip_endpoint_options_for_12_1.py