I have a topic table, including content title author and other information, accompanied by a Topic_extra contains the number of replies, likes, satisfaction reply, update and other information. A total of 14 fields, each table after the split is only six or seven, I think the table can be small, small bar.
The contradiction is that when the query needs to be federated, plus the user table, and other permissions control may be 4 tables join together, but write most of the Topic_extra. I wonder if I can solve this contradiction through the view, or what do we usually do, why?
Reply content:
I have a topic table, including content title author and other information, accompanied by a Topic_extra contains the number of replies, likes, satisfaction reply, update and other information. A total of 14 fields, each table after the split is only six or seven, I think the table can be small, small bar.
The contradiction is that when the query needs to be federated, plus the user table, and other permissions control may be 4 tables join together, but write most of the Topic_extra. I wonder if I can solve this contradiction through the view, or what do we usually do, why?
4 table do join a bit more, if it is I may not do a join, because the requirements are different, the data to be extracted is also different, can be associated with the ID extra field to fetch data, combined with the cache, high performance will be OK