> We have our own ORM layer rather than using another one like Propel. > Among other advantages, this allows CakePHP to innovate on its own.
technically cake's datalayer is not ORM. it doesn't work with objects (at least not in the way ORM's do). I know this is on the roadmap for 2.0 or whatever, but right now the data abstraction layer is less functional then an ORM solution like propel. I don't want cake to look bad because i certainly don't think it's bad, i think it's good, i use it for several projects. But i think we should be honest with ourselves. Cake certainly has it's advantages over other frameworks but it's not like it is better on *everything* PS: i don't like the "metadata hell" (overuse of configuration files, especially in xml format) either. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
