d8d2fe6990
implements bug #1021767 To sync db migration, for now use temporary script tools/dbsync. Modify it to point to your db url (example 'sqlite:///ceilometer.db' or 'mysql://user:mypass@localhost/ceilometer'). Also ensure the database_connection= in conf files point to same db url. Change-Id: I1c72b0a6b860738e94cf19666cb47db88ac9b251
26 lines
1.2 KiB
INI
26 lines
1.2 KiB
INI
[db_settings]
|
|
# Used to identify which repository this database is versioned under.
|
|
# You can use the name of your project.
|
|
repository_id=ceilometer
|
|
|
|
# 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=[]
|
|
|
|
# When creating new change scripts, Migrate will stamp the new script with
|
|
# a version number. By default this is latest_version + 1. You can set this
|
|
# to 'true' to tell Migrate to use the UTC timestamp instead.
|
|
use_timestamp_numbering=False
|