taizou @lion@computerfairi.es

There's a video https://item.taobao.com/item.htm?id=731232155720

Found another good console design. It's a bear
Model number is H8 but I can't find it for sale outside China atm
https://detail.1688.com/offer/719538095089.html

@Beanycatte@chitter.xyz yeah!!

I also found that "file per table" was actually ON but for that particular table it doesn't create a file for it, even if I dump and reimport the table? hello???
once again I'm going to fucking bed

Tried a few possible solutions for reclaiming the space without recreating the whole DB. None of them worked. Piss

@Rib 🫂 sorry to hear, I'm here if you wanna talk

Look at this cat https://www.youtube.com/watch?v=wIzx2lc6Wfc

We did it gamers. Deleted all the spam text. And how much space has that gained me? fuck all!!!!! because InnoDB will never give you space back once it's used it, if you have the "file per table" setting turned off (which is the default) it just dumps everything into that fucking ibdata file which can never get any smaller. The only thing you can do from here apparently is to dump all the DBs, wipe the whole thing and reimport them. I'm going to fucking bed

well my internet went down but i'm tethering off my phone to fucking finish this
I deleted all those orphaned slots/content entries and ran the script. the script actually found the orphaned text this time but threw an error when trying to delete it. so I ran another sql query to delete the text
THAT failed cos it ran out of space while trying to write a temp file so I'm now doing them 100 at a time

@mavica_again good, I'll keep posting
Or I would but my internet has just gone down

OK so what I figured out is that revisions are linked to content by the "slots" table, and the "slots" table suspiciously has 2888 entries referencing nonexistent revision ids, which is the exact same number of archived revisions that were purged
So I THINK I should be safe to delete those slots and Then delete the content entries corresponding to those slots and Then delete the text entries corresponding to the content entries

Sorry for posting through this btw

I Think what happened was the first script purged the references to the revisions in the "archive" table, meanwhile the second script is looking for references in the "content" table which was not actually touched by the first script
so uhhhhh I guess I can try and identify orphaned content entries myself and delete them and then run the second script and hope I don't fuck everything up

How did I even get here this has nothing to fucking do with Docker