search

fs-geofs / ErstiWeTool

signup & management platform for our freshmen's weekend
GNU General Public License v3.0
0 stars 1 forks source link

Database should have last_updated field #33

Open christophfriedrich opened 2 years ago

christophfriedrich commented 2 years ago

Right now we can't see in the database at what time someone opted out. Even the rows where the state is opted_out still have the creation timestamp in the timestamp column. I think there should be two timestamp columns, one for creation, one for last update.

Or keep a log of all opt outs? Because this year someone from the waiting list later opted out again :joy: So those time infos would be lost too even with the scheme suggested above.

noerw commented 2 years ago

Opting out results in a new token being created. As a result both timestamps are available technically, spread over the old and new token, you just need to follow the prev_user chain. Though I agree, having separate timestamps is better ;)