MySQL foreign key constraints break `mysql.TruncateAll()` (`TRUNCATE TABLE`) calls about pop HOT 1 CLOSED

That might be a very bad idea.
I'm no MySQL engineer, so I can't say for sure this is a reasonable thing to do. I assume it is, because my read of SetupTest() is that it's dropping all data from the database, so there should be no data left to be orphaned, but... I don't know very MySQL well, so I don't know what corner cases (or not-so-corner cases) that setting might impact.

Right now, I can't find a better option, even after using MySQL for years.

I'm not sure if it would be correct to modify TruncateAll() in that way.
Again I assume it would be, but I'm not familiar enough with the consumers of Pop to know if that would lead to surprising behavior. If foreign key constraints are set, truncations should fail. Would changing this function cause logic that should fail, to not fail? Would there be a clean way to add an argument or contextual setting to TruncateAll() that would let us control that behavior? Are there any uses of TruncateAll outside of SetupTest() for such a change to affect, anyway?

To answer that question, we have to check the other DB behavior for pop supported dialects. If the other allow to truncate all the tables, even with foreign keys, we should do it.

from pop.