|  | 
| 基于以上的,我大致总结一下,请看看是否正确: 我查看了一下帮助
 CONSIDER FRESH
 This clause lets you manage the staleness state of a materialized after changes have been made to its master tables. CONSIDER FRESH directs Oracle to consider the materialized view fresh and therefore eligible for query rewrite in the TRUSTED or STALE_TOLERATED modes. Because Oracle cannot guarantee the freshness of the materialized view, query rewrite in ENFORCED mode is not supported. This clause also sets the staleness state of the materialized view to UNKNOWN. The staleness state is displayed in the STALENESS column of the ALL_MVIEWS, DBA_MVIEWS, and USER_MVIEWS data dictionary views.
 
 
 --------------------------------------------------------------------------------
 Note:
 A materialized view is stale if changes have been made to the contents of any of its master tables. This clause directs Oracle to assume that the materialized view is fresh and that no such changes have been made. Therefore, actual updates to those tables pending refresh are purged with respect to the materialized view.
 
 我下面要做的:
 1.将QUERY_REWRITE_INTEGERITY的值设置为STALE_TOLERATED,可以解决我的问题本身,但是如果数据库中其他的物化视图不是采用这种策略,则是会有影响的(是否是其他的不是这种策略的视图,也会被认为是更新及时,而导致基表/视图结果其实是不一致的);
 2.只是这张表采用这种策略,可以考虑
 
 alter materialized view js_mv_tlw_sett_f3_200503 consider fresh;
 但是要在session里指定;
 
 也就是说,如果想查询js_mv_tlw_sett_f3_200503 这种策略的视图的结果(实际是针对基表查询,使用查询重写)需要session级指定consider fresh;请问此时的QUERY_REWRITE_INTEGRITY 设置为什么是否已经没有关系?当前的我们是 enforce;
 | 
 |