Silverstripe Version:
3.7
Question:
An new requirement came up to ‘keep history of changes’ in the application I inherited. As my developer background is OLTP, my first ideas was to use the SQL feature ‘System-Versioned Table’ available in most recent versions of any SQL DBMS. (i.e. What’s new in MariaDB 10.3).
Reading about ’ versioning concepts’ in SS4 there was no reference to SQL and a focus on ‘campaigns’ requiring only 2 versions, hence I’m unclear if the SQL feature is actually usable in a SS-based application.
Has anybody tried this yet?