Support → Database in the AdminCP could report that this application's tables "have some problems", and offer to fix them with a long list of queries — creating a copy of each table, moving the data across, DROPping the original and renaming the copy.

Nothing was wrong with the database and those queries did not need to be run. The tables were correct. What was wrong was the application's own description of them: each index definition omitted one optional field, so the checker compared the description against reality, found a difference, and offered to rebuild the table to match a definition that was already true.

What it looked like

A wall of SQL on the Database screen, including DROP TABLE statements against live data. Alarming, and entirely unnecessary.

Was anything at risk?

No. The suggested queries rebuild each table to exactly what it already was, so running them was harmless — and not running them was equally harmless. No data was ever affected either way.

The fix

The index definitions now declare the missing field, so the check passes and the screen stops asking. Nothing in your database is altered by the update.

This affected several applications for the same reason and all of them have been corrected in the versions released alongside this entry.