removing duplicate MYSQL generated array results

[eluser]jedd[/eluser]
[quote author="darkhouse" date="1252659376"]
However, I don't really see the difference in overhead if you do it in the model or not. It has to be done somewhere, so might as well do it in the model and just send the appropriate data to the controller, then view.
[/quote]

Yeah, it's a tough one .. I mean, you have to wear the cost somewhere, of course. I like the idea of doing it in the model from an aesthetic perspective - it's the 'right place', so to speak.

The reason *I* would probably do it out in the view is so I could more easily re-use the output of the method in my model. That is, if it's got the full (redundant) selection of data on each 'row', it makes it much easier if you want to extract an element while keeping its context - in other words, you don't have to flatten out its hierarchy again, if you see what I mean.

But yeah, definitely six of one stuff and highly dependent on what else is going on in the app.