You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we can't see in the database at what time someone opted out. Even the rows where the state isopted_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 😂 So those time infos would be lost too even with the scheme suggested above.
The text was updated successfully, but these errors were encountered:
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 ;)
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 thetimestamp
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 😂 So those time infos would be lost too even with the scheme suggested above.
The text was updated successfully, but these errors were encountered: