How best to do an audit trail of changes (EASILY WITHOUT THE NEED FOR A DBA)

VFP9SP2 app, MariaDB 10 (MySQL) backend.

One of my clients asked about a history of price changes.  Easy enough to implement programmatically for the few price fields, but then I got to wondering if simply putting code in the ON UPDATE trigger to send the old record to a "history" table would be a more complete (and long term EASIER) solution, whereby my app would query the "history" table for changes.

Your thoughts for tracking price (or other) changes?

tia, --Mike

--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus