Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database should have last_updated field #33

Open
christophfriedrich opened this issue Nov 4, 2021 · 1 comment
Open

Database should have last_updated field #33

christophfriedrich opened this issue Nov 4, 2021 · 1 comment

Comments

@christophfriedrich
Copy link
Member

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 😂 So those time infos would be lost too even with the scheme suggested above.

@noerw
Copy link
Member

noerw commented Apr 3, 2022

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 ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants