Use database to track submissions #57

Closed
opened 2023-03-07 14:14:41 -05:00 by imcompiling · 3 comments
Owner

Currently have submissions being tracked by local memory and also by embedding the data into the verification message. Should remove that and create a new table in the database that handles submission tracking. This way information is presented more cleanly and also can survive the bot restarting.

Currently have submissions being tracked by local memory and also by embedding the data into the verification message. Should remove that and create a new table in the database that handles submission tracking. This way information is presented more cleanly and also can survive the bot restarting.
imcompiling added the enhancement label 2023-03-07 14:14:41 -05:00
imcompiling added this to the Agon Development project 2023-03-07 14:14:41 -05:00
Author
Owner

Makes #11 easier to do.

Makes #11 easier to do.
imcompiling added a new dependency 2023-03-29 19:29:28 -04:00
imcompiling added reference 57-submission-table 2023-03-29 20:30:50 -04:00
Author
Owner

Want columns for: submission message id, group id, category id, username, score, verification message id.

primary key is a combination of group id, category id, and username. this is to prevent a user from having more than 1 active submission per category.

The VMId is to be able to map the results to each database entry.

SMId is used to update the submission message after accept/deny.

Want columns for: submission message id, group id, category id, username, score, verification message id. primary key is a combination of group id, category id, and username. this is to prevent a user from having more than 1 active submission per category. The VMId is to be able to map the results to each database entry. SMId is used to update the submission message after accept/deny.
Author
Owner

Completed in #69

Completed in #69
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: imcompiling/agon#57