I see MariaDB has an auditing module... if that isn't overkill.

Otherwise it can't be very hard to pull together a list of checksums of table structure, with their constraints/indexes (and maybe a few more things). Then run that daily/hourly/whatever, redirect to timestamped files, and make sure you notice when a diff appears.

(Postgres has a configuration setting 'log_statement' that can be set to 'ddl', which logs CREATE, ALTER, and DROP statements. Ideal, but now you have to go through the social tension of getting your client to migrate to postgresql :P )

[1] postgres runtime config - Logging what

In reply to Re: Tracking and deploying changes in (MySql/Maria) DB schema ... by erix
in thread Tracking and deploying changes in (MySql/Maria) DB schema ... by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.