Since PHP(4) has better support for arrays than objects, we've decided to play to that and use it for database results. The same architectural principles apply, just in a modified way. Logic can still be embedded in model objects using callbacks and custom methods. See http://c7y.phparch.com/c/entry/1/art,mvc_and_cake
On Jun 23, 6:40 pm, Howie <[EMAIL PROTECTED]> wrote: > Hi there. This is my first post. I'm just learning Cake, coming from a > strong Java background. I like what I've see so far, but am a little > confused with the Model part of the MVC implementation. Perhaps I'm > missing something. > > My understanding of MVC, is that the Model represents the data. In > Cake, the Model appears to be nothing more than an a DAO (Data Access > Object). Is this correct? > > If I have a Model Class representing a blog post mapped to a database > table, I would expect that the Class have attributes for each database > field. What I get instead is a set of database helper methods > returning results as a multi-dimensional array. There is no Object- > Relational Mapping. > > As I say, perhaps I'm missin something. Google suggests there is an > ActiveRecord implementation in Cake somewhere. Not too familiar with > this pattern, bt perhaps this is what I'm after? > > Can someone please point me in the right direction? > > cheers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
