> No problem. It's not a big deal. It is a bit misleading that the Cake > home page states that it supports ORM tho' :-(
I disagree. I think that you are looking for a narrowly defined approach for OR mapping. The approach that you describe is quite similar to how CakePHP does it, even though the syntax is different. For example, toy = new Toy(); toy.size = 'value'; toy.price = 'value'; toy.weight = 'value'; toy.save(); Compared to: $toy = new Toy(); $toy.set(array( 'size' => 'value', 'price' => 'value', 'weight' => 'value', ); $toy.save(); That'll work in CakePHP. How is that conceptually different? More importantly, you need to look at what CakePHP does and how it makes programming web applications easier. The fact is, I almost never create objects and save data in this fashion. The framework automates much of this kind of work. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
