[Zeitgeist] [Bug 566898] Re: Log DB file should be versioned

2010-08-06 Thread Siegfried Gevatter
** Changed in: zeitgeist
Milestone: 0.3.4 = 0.4.0

-- 
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: Fix Released

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


[Zeitgeist] [Bug 566898] Re: Log DB file should be versioned

2010-06-11 Thread Markus Korn
** Changed in: zeitgeist
   Status: Fix Committed = Fix Released

-- 
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: Fix Released

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


[Zeitgeist] [Bug 566898] Re: Log DB file should be versioned

2010-05-27 Thread Mikkel Kamstrup Erlandsen
** Changed in: zeitgeist
   Status: In Progress = Fix Committed

-- 
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: Fix Committed

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


[Zeitgeist] [Bug 566898] Re: Log DB file should be versioned

2010-05-25 Thread Mikkel Kamstrup Erlandsen
@Seif: *pssst* look under the Related Branches header, but don't tell
anyone ;-P

-- 
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: In Progress

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


[Zeitgeist] [Bug 566898] Re: Log DB file should be versioned

2010-05-18 Thread Mikkel Kamstrup Erlandsen
** Branch linked: lp:~kamstrup/zeitgeist/schema_versions

** Changed in: zeitgeist
 Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)

** Changed in: zeitgeist
   Importance: Undecided = High

** Changed in: zeitgeist
   Status: New = In Progress

-- 
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: In Progress

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