ladder fixed

[Mistral]

so guys i just found out ladder wasnt working since november 15 so i fixed it and all 4992 games since 15 to 27 november got loaded and parsed as normal

i found out it was because we have played so many games since 2020 when database was last cleaned so that we got so many games its overflow and got out of memory
lol wtf 

so i maked new table for new reports

p.s. someone pls not forget to remind me to change database table again in 4 years

[Mistral]

my ladder script and old are launched from same file and use same functions later
so i cannot fix mine without fixing old too 

[Dudakurten]

Thanks mistral!!!!

[{Lance}]

so guys i just found out ladder wasnt working since november 15 so i fixed it and all 4992 games since 15 to 27 november got loaded and parsed as normal

i found out it was because we have played so many games since 2020 when database was last cleaned so that we got so many games its overflow and got out of memory
lol wtf 

so i maked new table for new reports

p.s. someone pls not forget to remind me to change database table again in 4 years

Erm.  You should absolutely never have OOM problems for a database.  Ever.  The only thing that would cause such non-sense is if you tried to load the entire table on a single page which would be stupid (this is what pagination and/or queue systems are used for)  So this smells of bad code rather than a DB to large.  I deal with TB size tables daily (PHP/MariaDB),  this isnt a DB issue.  Just fix the code and you wont have to be reminded every so often

If you need assistance fixing OOM issues in code,  there's plenty of us out here that could easily assist with that.

[Mistral]

if you tried to load the entire table on a single page which would be stupid

well YES this is actually EXACTLY what happens here 
i not writed all ladder from 0
i used old Blid ladder system that is in here (https://ladder.war2.ru)
and after his ladder counted all games i also insert my code in between and check for my random maps and count for separated tables for (https://ladder.war2.ru/index_mist.php)

so ye its basically the intire system is fucked up and cursed, but it works and worked all those years after Blid maked it.

to fix it, its needed to change the entire system and make all from 0, which is too hard for me now

[{Lance}]

to fix it, its needed to change the entire system and make all from 0, which is too hard for me now

This is a total cop-out.  You could have antropic's Claude fix it in about 3 seconds.  Literally.  Just make a new "project",  paste the source of the ladder into the project as text,  label it as "files",  dump the DB structures with the describe command,  put it in another text entry called "db schema" and then tell it to fix the OOM error by using queue systems and pagers.  It will take about 15-30 minutes to do.  The ladder code is so small that it would be perfect for a chatbot to fix because it can see the entire codebase.  You could even tell it to convert it to a complete OOP project by asking it to use an MVC methodology.  And it wouldnt result in people losing stats either.  Since the chatbot could see the schema,  if the DB is unusable,  you could simply have it create a porting script for the DB and the new schema that it comes up with and it would port the old data to the new format (if its even needed which I highly doubt,  the problem isnt the DB, it's the code and it's probably 1 line at that)

It's so easy that someone with literally no coding experience at all could fix it.  All they would need is the source to start with.  Saying it's "to hard" is just a complete lie because we both know it's NOT hard   with or without a chatbot.