Should models representing a single row return data generated using multiple rows?

It would be right to have extended ArrayObject ( http://php.net/manual/en/class.arrayobject.php ) or other container class to run methods for collection. Try to modify query methods to return data in your custom collection class instead of array if specified.

There's nothing inherent to MVC that says "each model instance should represent one row." Often in MVC frameworks the model (as seen by the controller, at least) is entirely ignorant of the data store and doesn't have any concept of or direct mapping to a "row." This isn't necessarily the case with ORMs but a model needn't adhere to an ORM's constraints.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.