[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4626: --------------------------------------- Those are essentially correct - it's just providing an avenue for full refresh beyond TTL. We need the transitive graph of all source tables contributing to the view, then any modification to those would count as a modification that yes would be tracked on the status table. We already have logic with the result set caching functions similar to this. The cache tracks all objects that contribute to a given result and looks for modifications after the creation of the cache entry to invalidate the entry. That's certainly possible to do. Any alter view / alter procedure may mean that we'll have to add / drop triggers. The intent was to use some proportion or percentage based upon the rows * columns. -- This message was sent by Atlassian JIRA (v7.2.3#72005)