d6fbf12989
Remove all trailing spaces and tabs in every file in the project. People have editors configured to do this, which causes them to accidentally make little whitespace changes in unrelated commits, which makes those commits harder to review. Better to fix them all at once. Change-Id: I17d89f55f41d8599e0ab1a31f646cd161289703e
26 lines
1.3 KiB
INI
26 lines
1.3 KiB
INI
[db_settings]
|
|
# Used to identify which repository this database is versioned under.
|
|
# You can use the name of your project.
|
|
repository_id={{ locals().pop('repository_id') }}
|
|
|
|
# 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={{ locals().pop('version_table') }}
|
|
|
|
# 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={{ locals().pop('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={{ locals().pop('use_timestamp_numbering') }}
|