@Miles J: That's why a toggle would be nice in the core to use associative or full fledged model objects.
It would be nice to run model functions off the returned object in either the controller or view without having to set the model's id. Furthermore, if you needed to manipulate two objects of the same model in one controller action there's no easy way to execute their model function without passing the id in and handling that in the model. It's a little sloppy, and it doesn't have to be. /shrug But what I'd really want are: 1) full fledged cake console 2) migrations I'd be a real happy camper with those two =) Nick On May 13, 3:40 am, Miles J <[email protected]> wrote: > @nurvzy - Returning objects from a mysql resource and slower then an > associative array. I for one would hate to have to use objects within > views. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
