History

Sean Bright e5e9692738 res_pjsip: Fix alembic downgrade for boolean columns. When downgrading, ensure that we don't touch columns that didn't actually change during upgrade.		2024-03-20 12:09:45 +00:00
..
cdr	Remove as much trailing whitespace as possible.	2017-12-22 09:23:22 -05:00
config	res_pjsip: Fix alembic downgrade for boolean columns.	2024-03-20 12:09:45 +00:00
queue_log	ast-db-manage: Synchronize revisions between comments and code.	2023-06-12 14:40:15 +00:00
voicemail	app_voicemail_odbc: remove macrocontext from voicemail_messages table	2024-01-17 15:01:38 +00:00
.gitignore	alembic: Update list of TLS methods available on ps_transports.	2023-11-28 19:54:33 +00:00
README.md	contrib: Spelling fixes	2021-11-16 06:02:11 -06:00
cdr.ini.sample	alembic: Adjust sippeers, queue_members, and voicemail_messages tables.	2014-08-06 17:04:08 +00:00
config.ini.sample	alembic: Adjust sippeers, queue_members, and voicemail_messages tables.	2014-08-06 17:04:08 +00:00
env.py	Remove as much trailing whitespace as possible.	2017-12-22 09:23:22 -05:00
queue_log.ini.sample	queue_log: Add alembic script for generate db table for queue_log	2019-11-22 15:33:29 +00:00
voicemail.ini.sample	alembic: Adjust sippeers, queue_members, and voicemail_messages tables.	2014-08-06 17:04:08 +00:00

README.md

Asterisk Database Manager

Asterisk includes optional database integration for a variety of features. The purpose of this effort is to assist in managing the database schema for Asterisk database integration.

This is implemented as a set of repositories that contain database schema migrations, using Alembic. The existing repositories include:

cdr - Table used for Asterisk to store CDR records
config - Tables used for Asterisk realtime configuration
queue_log - Table used for Asterisk to store Queue Log records
voicemail - Tables used for ODBC_STORAGE of voicemail messages

Alembic uses SQLAlchemy, which has support for many databases.

IMPORTANT NOTE: This is brand new and the initial migrations are still subject to change. Only use this for testing purposes for now.

Example Usage

First, create an ini file that contains database connection details. For help with connection string details, see the SQLAlchemy docs.

$ cp config.ini.sample config.ini
... edit config.ini and change sqlalchemy.url ...

Next, bring the database up to date with the current schema.

$ alembic -c config.ini upgrade head

In the future, as additional database migrations are added, you can run alembic again to migrate the existing tables to the latest schema.

$ alembic -c config.ini upgrade head

The migrations support both upgrading and downgrading. You could go all the way back to where you started with no tables by downgrading back to the base revision.

$ alembic -c config.ini downgrade base

base and head are special revisions. You can refer to specific revisions to upgrade or downgrade to, as well.

$ alembic -c config.ini upgrade 4da0c5f79a9c

Offline Mode

If you would like to just generate the SQL statements that would have been executed, you can use alembic's offline mode.

$ alembic -c config.ini upgrade head --sql

Adding Database Migrations

The best way to learn about how to add additional database migrations is to refer to the Alembic documentation.