Real-Time Caching in OLTP

OLTP's - When a table is cached (Materialized View, Cached Tables) there is a mandatory parameter that signifies frequency the cache should load (Incremental/Full Load). 

But when the data is updated or inserted for a few rows in a table per transaction it would make more sense to Real-time cache them. 

How you ask? 

A DML Trigger with a compiler hint seperating the parent and child transaction. pragma AUTONOMOUS_TRANSACTION in case of Oracle and likewise in other DBMS. This way Real-Time Caching can be achieved but if you want to cache in a different flavor of the Database make way for Real-time ETL that helps both Real-Time Caching and Real-Time ETL...