With an old DB in production for years it becomes necessary to clear some of the tracking tables. The issue at hand is that some of those tables are used for other things - exercices results.

The idea would be add:

- a screen - in statistics - to get rid of entries older than x years/months.- a screen to re initialize the running totals - it does't make much sense to have a tracking of os/navigator/countries that take into account entries over several years.

A related feature would be to to have running totals per months. I.e. all people from country x in month 2012 01.

Now if I got things alright some tracking tables contain exercise results. Another feature would be to move them to a table called c_quiz_result and keep only tracing information into tables called tracking.

History

It's OK to plan this for the future. Actually, there might be an old task about it in the list. Let's say that most of the time you might have good reasons to keep track of older results (several user institutions are actually required by law to keep records of that for... years).

In my opinion, we should develop an archiving mechanism where the data is automatically put into track_archive_[year]_* tables when they are past 2 years age, for example. The data would still be available for the admins, but through extended interface only allowing queries between two dates in the same year.