Thanks Jonathan.
I guess I'm being a little pendantic about the Model, but then again,
I did lose time trying to understand it, as I's asumed it did much
more than it appears to do. What happens under-the-hood is great, and
keeps the code clean, but it's not ORM as I understand it.
>From my Java OO experience, the real benefits gained from ORM is
mapping relational data back into into an object graph.
So, my findUser($id) method might return a User with Roles that can be
accessed as $user->getRoles() rather than $user['User']['Roles'].
In your example, setting an array of name/value pairs is not
conceptually) the same as setting class attributes. If my model is to
become thick with business logic, then it should be able to operate as
a class instance.
Can my Toy class encapsulate logic such as:
if ($this->price < 9.99) then {.. } ?
The examples of Fat model that I've seen all seem statelss with
repsect to the object attributes.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
