title: Best git mysql versioning system?
body: <p>I've started using git with a small dev team of people who come and go on different projects; it was working well enough until we started working with Wordpress.  Because Wordpress stores a lot of configurations in MySQL, we decided we needed to include that in our commits.  </p>
  
  <p>This worked well enough (using msyql dump on pre-commits, and pushing the dumped file into mysql on post-checkout) until two people made modifications to plugins and committed, then everything broke again.</p>
  
  <p>I've looked at every solution I could find, and thought Liquibase was the closest option, but wouldn't work for us.  It requires you to specify schema in XML, which isn't really possible because we are using plugins which insert data/tables/modifications automatically into the DB.<br>
  I plan on putting a bounty on it in a few days to see if anyone has the "goldilocks solution" of:</p>
  
  <p><strong>The question:</strong><br>
  Is there a way to version control a MySQL database semantically (not using diffs EDIT: meaning that it doesn't just take the two versions and diff it, but instead records the actual queries run in sequence to get from the old version to the current one) without the requirement of a developer written schema file, and one that can be merged using git.</p>
  
  <p>I know I can't be the only one with such a problem, but hopefully there is somebody with a solution?</p>