You implemented primary and foreign keys in your database, sprinkled with unique and check constraints, all to keep your data in the best shape possible.
But what about data-rules that involves multiple tables, apart from referential integrity?
For example: the total amount of the order must be the sum of the related order lines. How can you guarantee that this rule is always true?
Changing amounts at order line level will impact this rule, as well as changing the order total amount.
Lots of database developers will try to implement a watertight solution with triggers while working their way around mutating table issues.

You wish there was something simple ... and there is: SQL Assertions.
SQL Assertions have been around since the early 1990's - at least on paper.
Until now there was no database vendor that actually implemented SQL Assertions. Oracle is the first vendor that has cracked the code and implemented SQL Assertions in Oracle Database 23ai.

This session will show all aspects of SQL Assertions, with many real world examples.