Project

General

Profile

Bug #2560

Implement revision system for new revisions

Added by Michael Lee about 14 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
ArchiveDB
Target version:
Start date:
10/03/2006
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2560

Description

Bob and Forbes have lists of revisions needing to be made. I have written some code that will digest and archive this simple list. Due to connectivity issues, it may be easier for Forbes to push the "GO" button.

History

#2 Updated by Michael Lee over 11 years ago

Revision system now works on the new archive database. There are 3 tables of interest:

1) revision - this is from the VegBank model which stores the old (and now also the new) values involved in the revision, also tablename, attributename, and primary key value.
2) revisionProject - I'm not sure this is needed, but it groups revisions together in a package of revisions.
3) revisionsQueue - this is a place where pending revisions can be stored (even before the plots are in the database) and then implemented, based on the revision project number. It's possible to include the old value in the field, or you can leave that blank and update the value without worrying about it.

#3 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 2560

Also available in: Atom PDF