This appears to still be an issue that hasn’t been resolved. Are there any solutions to ‘lock’ Strapi from making DB changes like this?
We’ve been running into this same issue running Strapi 4.22.1 Postres db in ‘production’ environment. We just had a table truncate itself and lost hundreds of records.
No one on the team made any schema changes since last week (schema changes is usually when we’ve noticed data getting dropped/lost which still isn’t good but something we began getting used too).
We’re sort of at a loss here as to why this occurred and what to do to prevent it. At this point we just had a meeting about pivoting and getting rid of Strapi completely. Can’t go into a true production environment when data just vanishes.