It seems like all of the pieces of software out there which do this either want you to jump through a bunch of registration hoops, or download a whole suite of tools and spend awhile figuring out which one you actually need.

--
My first thought is to use mysqldump to export the database snapshots, and then use "diff -minimal a.sql b.sql" to find the differences.
mysqldump -uuser -ppassword test > a.sql
# do some stuff
mysqldump -uuser -ppassword test > b.sql
- mysqldump -uuser -ppassword test > a.sql
- # do some stuff
- mysqldump -uuser -ppassword test > b.sql
That diff will give you output like this though, which I'm guessing isn't going to be the easiest thing to decipher with a real data set. I suppose it's possible though.
joebert@sr1123wm:/tmp$ diff -d a b
37c37
< INSERT INTO `one` VALUES (123,122),(1,4);
---
> INSERT INTO `one` VALUES (123,122),(1,4),(123,122);
77c77
< -- Dump completed on 2010-05-13 22:28:48
---
> -- Dump completed on 2010-05-13 22:28:59
- joebert@sr1123wm:/tmp$ diff -d a b
- 37c37
- < INSERT INTO `one` VALUES (123,122),(1,4);
- ---
- > INSERT INTO `one` VALUES (123,122),(1,4),(123,122);
- 77c77
- < -- Dump completed on 2010-05-13 22:28:48
- ---
- > -- Dump completed on 2010-05-13 22:28:59
Which if you just want to know which tables changed, those hex offsets could be traced back to the CREATE TABLE statements in b.sql to find out which table changed.
Strong with this one, the sudo is.