i thought the db was relativly simple not as i said it
table 1:
per map:
time, completion
table 2:
who, points (oh no my normal form), completions[], teamcompletions[]
table 3/4:
map, (team), best time, completions(edited)
Tater
Deen does databases as a job so I assume he knows the most of anyone
If you want to work on the top5 issue, I think it's settled that a separate table with only top records of people would help the most, and you can maintain one using triggers
If you want to work on the top5 issue, I think it's settled that a separate table with only top records of people would help the most, and you can maintain one using triggers
Materialize aims to solve the incremental update issue, but as I said it required an absurd amount of ram. I didn't try Timescale
09:52
I thought Timescale was more for time series data, our data isn't very dense in time per map or per player. It is however kinda dense in time in general without filtering. So maybe it might work decently
Also team finishes are a thing, there's non fixed team size and the website needs a link to everyone's profile so you can't just put it in a string I think
I had a single idea for a clever index trick that I was going to try but not having the actual indexes was an imaginary blocker I made, I'll try it in a couple days.
you can get through the gap with downspeed, it works similar to going through the these freeze tiles i dew but its not about position but speed(edited)