Zend Framework has a deliberate design goal that it requires no configuration files -- especially not XML configuration files. :-)
The Prado SQL mapper solution you cite uses an XML configuration file to define the map between object properties and relational attributes in a database schema. Instead, I would suggest that the data mapping be done in a Model class, as PHP code. There's no need for another component that does this. It would be hard to write a generic component that is both simple to use and also supports the majority of use cases. Such a one-size-fits-all solution would be at risk of becoming bloated with lots of special-case code that isn't useful to most people. So Zend Framework provides no abstract model class, leaving it up to the application requirements to dictate how to implement data mapping in model classes, on a case-by-case basis. Regards, Bill Karwin > -----Original Message----- > From: Sam Davey [mailto:[EMAIL PROTECTED] > > Has anyone involved with the Zend Framework ever considered > proposing a Zend_Data_Mapper?
