MVC架构决策 - 如何将现有方法重新分解为控制器/视图和数据库访问

Question

Consider the following scenario:

Page written in classic ASP or PHP, which is rendering a data report (series of HTML tables for simplicity). There is one main database query and then multiple sub queries as the page renders. The report is split into sub panels, which correlate to a sub query. Therefore:

1. Main database query.
2. Loop over result.
3. For each row, execute sub query and render report panel.

How would you architect a similar report using the MVC pattern?

This can be split into two parts:

1. Efficiency at database level of multiple queries, which are dependent on values from an outer query.
2. If all data was processed and prepared in the controller, would this also be deemed inefficient if looping within the controller and then again in a view to render. Could sub controllers be used or sub panels, which encapsulate smaller sections of logic i.e. loading data and rendering report panel.

Appreciate this may look a bit vague but I'm interested in how you would approach the solution.

Answer 1

My final solution had all data retrieval in a repository and then various bits were aggregated in the controller ready for display in the view.