Like performance issues or something? Basically I will have some Views whose data will be coming in across different models and I just want to have the data sent back to be the ones that I need, and really don't like the arrays CakePHP models send back.
So just get the aggregate data, transform it and populate the object then send that back to the controller to pass on to the view.
Yes it's extra work but if it doesn't cause any issues, I think it'll be worth it.
So any problems with this way of doing things? Thanks.
Converting to objects would be small overhead but shouldn't pose any major issues performance wise. Though it could make maintaining the app difficult for others like burzum commented. By augmenting the way the framework works you will lose lot of its benefits. Eg. passing objects to views means the helpers won't be able to do any "magic". If you dislike the fact that CakePHP's models return arrays then perhaps you should not be using CakePHP.