I did, but I missed that bit. Which is bad! Having database versioning rolled in makes it interesting to people like me as well.

If the developers are reading this: move that info up to the top of the page! Currently it's buried down in the "Features" section, making it easy to miss. Don't hide your light under a bushel :-)

Very valid point, we have just updated the website. Thanks!

I usually add a commit hook to run 'mysqldump'. Then you get a matching database snapshot along with the source code.

TIP: For better diff's use "--skip-extended-insert --skip-dump-date".

A nice gui on top of that is welcome (although I'm not sure about the $30K).

Why mysqldump instead of using the binary log? Just dump the result of SHOW MASTER STATUS to a text file in your git directory, back up your binary log files on a regular basis, and then you just use the stop position feature of the binlog utility[1] to restore to that point in time from the binary logs. A lot faster than doing mysqldump and a lot less likely to lock tables or slow down your database.

[1] http://dev.mysql.com/doc/refman/5.0/en/point-in-time-recover...

Interesting - thats the most compelling part and it looks like they missed highlighting that completely on the landing page.

Fixed that. Thanks.

mysqldump daily into the git repo folder?