title: Crash resilience of InnoDb vs. MyISAM
body: <p>We run a MySQL server on Windows. Sometimes, Windows crashes, and leaves the database in a corrupt state ("Duplicate entry for key 'PRIMARY'" messages though the key is auto-generated; that can be repaired with a "Repair table" command).</p>
  
  <p>I have seen that problem with MyISAM tables only, never with an InnoDb table. Did that happen by chance, or is InnoDb with its extra code for transactions actually more resilient towards such failures?</p>