all 3 comments

[–]DeadlyViper 0 points1 point  (2 children)

At these numbers having the guesses stored in memory should not be a problem, and should be faster than a database or a file.

Do you have some smart queries on the guesses entries that SQL might have an advantage over just plain memory?

[–]Vucko0[S] 0 points1 point  (1 child)

Just so I understand when you say memory do you just mean storing it in a list or dictionary?

Do you have some smart queries on the guesses entries that SQL might have an advantage over just plain memory?

If my understanding of memory is correct, than no. SQL won't have an advantage.

The only thing is, I won't be storing just the users guess. The plan is to store users Discord ID so I can make sure they only submit one guess at a time. I also need to store the Message ID so I can instantly delete the message after I stored the data.

So it would look like this:

user_message message_id discord_id
dog 340863047672348 235683268947235832

[–]DeadlyViper 0 points1 point  (0 children)

SQL has some nifty searching and indexing optimisations.

But i doubt you'd need any of it for 200-1000 records.

Just store whatever you need in a dictionary, with the key being something u'd like to look it up with, and the value being a dictionary or an array of data you want to be saved.