Last modified 14 years ago Last modified on 02/03/09 12:19:20

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=S2S_PERSIST_ARCHIVING_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block



Since the server will use the base persistence module, it is going to use the same persistence schema. Having in mind that the server will store every resource change, the persisted information will certainly be too much.

Task requirements

Design and implement a model for storage archiving. Think about the following aspects:

  • Archiving old resource changes.
  • Dealing with old comments.
  • Archiving unused accounts.

You must also revise the current persistence of changes - is there a way to store less data without affecting the performance of the change manager. For this, it is good to implement this task together with the ones, concerning about changes.
Make decisions on these and apply them.

Task result

Source code.

Implementation idea

1st: Implement this task together with the PRO_CHANGE tasks (they are too much, so they will not be listed here).
2nd: Think out just the mechanism for archiving, apply it to the currently persisted objects. Changes' shrinking can be implemented with the next (main) revision.

In chronological order:

How to demo

Show the code, run the tests (if any).


(Describe your design here.)


(Describe and link the implementation results here (from the wiki or the repository).)


(Place the testing results here.)


(Write comments for this or later revisions here.)