Thought it's obviously better done this way. ( and easier documented)

my crazy idea: Have a cron job doing hourly (or so)

mysqldump ...
git commit ...
[download]

If the cron job is scheduled often enough, it would register the modifications with enough granularity.

This is not crazy. It works. We did it like this with a huge MySQL DB for about 10 years. Best regards, Karl

«The Crux of the Biscuit is the Apostrophe»

perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

Maybe I should have been more explicit about needing the incremental steps (i.e. ALTER TABLEs)

So you need auditing. The audit plugin [1] seems to be made for this. As expected it has a QUERY_DDL setting which is pretty much what you seem to need.

[1] https://mariadb.com/kb/en/library/mariadb-audit-plugin-log-settings/

This looks good, will try it out, thanks! :)

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}