And pre-request feature may be we should improve the performance of insert
into select ，but this may be not pre， post may be also fine
Thanks
Yang Zhengguo
陈明雨 于2022年6月26日周日 11:55写道：
> I have read the DSIP, and I think the Instructions for use are clearer,
> but we need more detail designs.
The full update does not increase the complexity of the user's use. Under
normal circumstances, the user also needs to create a view, and the normal
view also needs to be calculated in time. Using a multi-table materialized
view is equivalent to caching some results. In order to reduce the user's
d
I have read the DSIP, and I think the Instructions for use are clearer, but we
need more detail designs.
For example:
1. how to "refresh" the mv
If we use "insert into select", Is there any difference between this and
the user using a crontab script outside to refresh. Does this increase in
I'd like to propose the support for Multi-table materialized view.
At present, materialized views can be created on a single table, and can
use pre-computed results to achieve query acceleration, but support for
multi-table scenarios cannot be realized. Many query scenarios are
relatively simple a
