Recently met a project, the problem of a complicated common view view_a connection, more needs to be view_a save the results of a query to a list within table_b for subsequent operations to modify table_b within the state of the status column, so view_a table_b process cannot through regular drop table_b to create generate table_b way, can only be assumed according to generate documents within view_a time column or on the ID column, the incremental synchronization changes into table_b, said a lot of people use materialized views to update regularly, I always tried to failure, the composition of view_a too complicated throughout a lot of table, broken down into simple statements don't, materialized views do not support to the view again, please everyone a great god can give you an example, do something, can tell me how?

CodePudding user response:

Their posts, their junction, which has been done,