Esko Arajärvi / is on Nostr

"9f73e47b50766e24d9cc6cc0fa582012a18a5e1398af97d916879c70c1501a34011cb1e0a37d61ebecb8e71b65a14b02c0439d8dda66b0445ae6cbdb99af0529"

Last Notes

2025-03-14 18:47:00

- reply

@nprofile…ktgr Weirdly that sounds like it has somehow lost any reference that such table exists. But the check table command still found it. Or at least a reference to it.

2025-03-14 18:39:27

- reply

@nprofile…ktgr Apparently, if all else fails, try these:
mariadb.com/kb/en/innodb-recov…

2025-03-14 18:35:41

- reply

@nprofile…ktgr Are you able to dump the table data with:
mysqldump –u user –p db_name table_name > output_file

2025-03-14 18:32:40

- reply

@nprofile…ktgr Damn. That sounds more serious. 🙁
I'm not sure where to start digging for the data next.

2025-03-14 17:27:20

- reply

@nprofile…ktgr You need to include the table name in back-ticks, because there is a dash in the name of the table.
ALTER TABLE `post-user` FORCE;
This should be completely safe to run, but as always, when manually tweaking things, take a backup beforehand, if possible.

2025-03-14 16:37:28

- reply

@nprofile…ktgr You can use ALTER TABLE tbl_name FORCE to perform a “null” alter operation that rebuilds the table. I have successfully repaired corrupted tables with this.
mariadb.com/kb/en/alter-table/…