Adding logic to the batabase upgrade.

Browse source

1. Introduced a new db table "db_version_history" to hal-default.db. The table contains a list of db version. Every version has some parameters:
- 'db-version' (int) - A db version number. table 'conf', key 'db_version' points to this.
- 'force-upgrade' (default:0) - If 1 then force the upgrade to this version
- 'clear-internal-aggr-data' (default:0) - If 1 then clear all internal aggr data before upgrade.
- 'clear-external-aggr-data' (defualt:0) - If 1 then clear all external aggr data before upgrade.
The db table 'conf', key 'db_version' has to point to the db version to upgrad to. Only forward upgrades are supported.

2. Modified HalContext to act accoring to the parameters in the new db table.


Former-commit-id: 19bd87ade3129f3fc0c51f0e1b94f71dc854d792

...

This commit is contained in:

Daniel Collin 2015-12-21 14:09:51 +01:00

parent b391e3a5e1

commit 275ffd97c2

2 changed files with 31 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

BIN

hal-default.db

View file

Binary file not shown.