search

ghbolivar / cropplanning

Automatically exported from code.google.com/p/cropplanning
0 stars 0 forks source link

HSQLDB Module Upgrades #21

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The database should store metadata about the last "known" version of the
HSQLDB module. (ie, which version was last used to access/modify the db) 
When a discrepancy is found (eg, the module is upgraded/updated), the
module should be able to "upgrade" the db to match the current
specification.  This should be incremental.

ie
  v0.0.8 ==> v0.0.9: "ALTER TABLE <cropplan> ADD COLUMN ..."
  v0.0.9 ==> v0.1.0: "ALTER TABLE crops_varieties ALTER COLUMN ... RENAME ...

and so on.  Then, if say a users upgrades from v0.0.8 to v0.1.0, all
statements in between the two would be executed sequentially and would, in
theory, bring everything up to parity.

Original issue reported on code.google.com by cropplan...@gmail.com on 2 Feb 2008 at 4:16

GoogleCodeExporter commented 8 years ago

Original comment by cropplan...@gmail.com on 2 Feb 2008 at 11:12

GoogleCodeExporter commented 8 years ago 
This capability was added in the PA2 release.

Original comment by cropplan...@gmail.com on 4 Mar 2008 at 1:45