You should schedule a "create or replace table" statement every N hours/days/etc. It will be effectively just the same as a scheduled materialized view refresh.
seriously, does google "query" all the documents that you might be interested in? no, i argue google makes mat view(s) of your interests by querying the response database and specifically NOT the actual documents.
remember, google only needs to be "kinda" CORRECT, unlike a relational db. try 'plaining that to management.
the "t" at the end of "fact" implies past tense. if a materialized view is
a statement of fact then you are safe to deploy in a relational schema, i claim. think about it.
Comments
You should schedule a "create or replace table" statement every N hours/days/etc. It will be effectively just the same as a scheduled materialized view refresh.
seriously, does google "query" all the documents that you might be interested in? no, i argue google makes mat view(s) of your interests by querying the response database and specifically NOT the actual documents.
remember, google only needs to be "kinda" CORRECT, unlike a relational db. try 'plaining that to management.
I've been reading up on this as a potential solution; I may have to finally take it seriously and try it out.
the "t" at the end of "fact" implies past tense. if a materialized view is a statement of fact then you are safe to deploy in a relational schema, i claim. think about it.
https://www.protechtraining.com/blog/post/the-value-of-value...