##// END OF EJS Templates
Update changeset cache should use non-cache version of repo if given attribute is empty, it's easier to controll how changesets are udpated...
Update changeset cache should use non-cache version of repo if given attribute is empty, it's easier to controll how changesets are udpated The quick update logic in base controller get's cached version and updates, while any other call will use non-cached version

File last commit:

r835:08d2dcd7 beta
r3420:a6bef3e8 beta
Show More
migrate.cfg
20 lines | 1017 B | text/x-ini | IniLexer
fixed imports on migrate, added getting current version from database
r835 [db_settings]
# Used to identify which repository this database is versioned under.
# You can use the name of your project.
repository_id=rhodecode_db_migrations
# 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=db_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=['sqlite']