which is better, creating a materialized view or a new table?
- by Carson
I have some demanding mysql queries that are needed to grap same up-to-date datasets from 5-7 mysql tables.
I am thinking of creating a table or materialized view to gather all demanding columns from other tables, so as to increase performance.
If I create that table, I may need to do extra insert / update / delete operation each time other tables updated.
if I create materialized view, I am worrying if the performance can be greatly improved. Because data from other tables are changing very frequently. Most likely, the view may need to be created first everytime before selecting it.
Any ideas? e.g. how to cache? other extra measures I can do?