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.

Sign up for GitHub

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

Jump to bottom

DB: Add table for ticks #48

Open
F30 opened this issue Apr 14, 2019 · 1 comment
Open

DB: Add table for ticks #48

F30 opened this issue Apr 14, 2019 · 1 comment
Assignees
@rudis @F30
Labels
improvement Not a critical bug, but also not a visible feature

Comments

@F30
Copy link
Member

F30 commented Apr 14, 2019

At the moment, we assume that actual start and end times for ticks are equal to the theoretical ones as computed from start time of the CTF and tick duration. Additionally, the current tick is stored in the "scoring_gamecontrol" table.

For improved error handling and better insights, it would be beneficial to have an extra table which stores the actual start and end time for each tick. All fields storing ticks, which are just integer values at the moment, should then be converted to Foreign Keys.
@F30 F30 added idea Idea to be discussed, not yet ready for implementation improvement Not a critical bug, but also not a visible feature and removed idea Idea to be discussed, not yet ready for implementation labels Apr 14, 2019
@F30 F30 assigned rudis and F30 Apr 14, 2019
@F30 F30 mentioned this issue Feb 27, 2021
Closed
@F30
Copy link
Member Author

F30 commented Feb 27, 2021

Would also help for #66.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rudis rudis

@F30 F30

Labels
improvement Not a critical bug, but also not a visible feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rudis @F30