Hi Val, I realize this is not a trivial task but here are a couple of ideas.
1. Triggers that run an offline task outside of the database processes (perhaps an ignite instance) that sync the cache. Depending on the database, we could auto-generate the DDL for defining the trigger making it easier for the user. 2. Every database has a log file that includes all table changes can be parsed. I know ignite has a powerful engine that can parse files and update caches. Thank you, Satya -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-refresh-from-persistent-store-question-tp2078p2112.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
