What happens with the russer when we hit the RKG new year

[Pilen]

The current thought is that we want to delete them.

[Rotte]

The RKG new year maybe being July 1.

Could it be nice to keep information on which rustours there have been, and which rusvejledere and russer has been on them. I find it amusing to search back now...

[Pilen]

Perhaps, we would then have to keep track of the year for each rus in the database (rkg-year).
But should all the other information be deleted?

We could instead make another table entirely for old russer. then the rustours would have to check if the current year is the year of the tour and then decide where to get its information from

[Rotte]

Either we could have a flag for old_rus, which becomes 1 when we start a new year. Then the rustours would still know who was on their rustour etc.

Otherwise we could have another table for old russer with only name and rustour saved. Then when a new year starts the current russer was transferred to the new table, and all information about them except for name and rustour was deleted.

[valberg]

You can already figure out whether a rus is an old rus or not via the rustour reference. The Tours table has a year column which can be used.

Differentiating the data makes it harder to maintain. Stick to one schema and represent it differently based on existing data. Also the possibility to do statistics kinda gets ruined if you don't keep the dataset uniform.

Just my two cents :)