search

ghbolivar / cropplanning

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

CropDB should be versioned #51

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Users should have the options of "archiving" the current CropDB.  This
would basically just create a copy of the DB and save it for later use. 
Any subsequent changes to the DB would not affect the copies, and crop
plans would have to be linked to a particular DB, so that for example, the
2007 crop plan would always use the 2007 crop information, even though we
might have added, removed or changed cultural information since then.

This would pretty much only be useful as a reference tool.

Original issue reported on code.google.com by cropplan...@gmail.com on 5 Feb 2009 at 7:19

GoogleCodeExporter commented 8 years ago 
If we do this, each crop plan would need to point to a particular crop DB.  The
current cropDB could just be referred to as "CURRENT" or something, but each 
crop
plan that points to "CURRENT" would need to be updated to either point to the 
new
copy, or be left alone to point to what is still the CURRENT DB.

Original comment by cropplan...@gmail.com on 5 Feb 2009 at 7:30

GoogleCodeExporter commented 8 years ago 
Closing this issue.  Either implemented in 0.5.5 or no longer relevant.

Original comment by cropplan...@gmail.com on 17 Feb 2013 at 1:46