Flashback - Referential Integrity and Part vs. Whole

MariaDB's flashback process. ( https://mariadb.com/kb/en/flashback/ ) works by swapping INSERT and DELETEs and before/after rowimages for UPDATE. So, in particular, referential integrity should be maintained if you unwind an 'oops' table and triggers or other RI guardrails fire.

Question -- is there a capability to run the whole system (all databases and tables) and not just a table that someone oops'ed, by running mysqlbinlog and listing all the relevant binlogs? Are there additional steps or considerations to "backtracking" the entire database?


Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.