4934eca225
This sets up the framework for adding database migrations to run on the new api database. It splits migration commands so that they can run on the current 'main' database or the new 'api' database. bp: cells-v2-mapping Change-Id: I73dee6fd51b74bd670a6dffa07e875bf86891e97
21 lines
984 B
INI
21 lines
984 B
INI
[db_settings]
|
|
# Used to identify which repository this database is versioned under.
|
|
# You can use the name of your project.
|
|
repository_id=nova_api
|
|
|
|
# The name of the database table used to track the schema version.
|
|
# This name shouldn't already be used by your project.
|
|
# If this is changed once a database is under version control, you'll need to
|
|
# change the table name in each database too.
|
|
version_table=migrate_version
|
|
|
|
# When committing a change script, Migrate will attempt to generate the
|
|
# sql for all supported databases; normally, if one of them fails - probably
|
|
# because you don't have that database installed - it is ignored and the
|
|
# commit continues, perhaps ending successfully.
|
|
# Databases in this list MUST compile successfully during a commit, or the
|
|
# entire commit will fail. List the databases your application will actually
|
|
# be using to ensure your updates to that database work properly.
|
|
# This must be a list; example: ['postgres','sqlite']
|
|
required_dbs=[]
|