Public bug reported:
We should really store log DB schema version in the our sqlite. That way
we can do smooth upgrades without hacks. Not only that, but we can also
shave off a lot of SQL grinding at startup if we just check the db
schema version...
I am thinking a new table:
CREATE TABLE IF NOT EXISTS version_info (schema_name VARCHAR, version
INT)
This table will have one row for our initial use case, but we may add
more rows in the future. The schema_name of our core log db could be
"main_log" and on startup we'd do:
SELECT version FROM version WHERE name='main_log';
if version != expected_version : do stuff
else : no need to run all our initial sql
** Affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Milestone: None => 0.3.4
--
Log DB file should be versioned
https://bugs.launchpad.net/bugs/566898
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug description:
We should really store log DB schema version in the our sqlite. That way we can
do smooth upgrades without hacks. Not only that, but we can also shave off a
lot of SQL grinding at startup if we just check the db schema version...
I am thinking a new table:
CREATE TABLE IF NOT EXISTS version_info (schema_name VARCHAR, version INT)
This table will have one row for our initial use case, but we may add more rows
in the future. The schema_name of our core log db could be "main_log" and on
startup we'd do:
SELECT version FROM version WHERE name='main_log';
if version != expected_version : do stuff
else : no need to run all our initial sql
_______________________________________________
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
