Re: DB_DataObject performance

Bertrand Mansion wrote: > DB_DO should be ok for high traffic sites. The bottleneck comes from PEAR DB but > it could be worse (for instance, Propel is not usable without a compiler cache). Wondering how easy it would be to hack DB_DO in order turn all PEAR DB calls into native mysql_* ones... Maybe that 10 stupid regex based instructions would do the trick. And if well done, it could be applied to every new DB_DO release... > CRTX_DB is certainly faster as it uses PDO. That is if you use PHP 5 and live on > the edge. My experiences with PDO show that it is not as stable and consistent > as it should be... PHP4 is one of my customer's requirements. > There is also my own solution, Phreez, but I am writing a lot of unit tests > right now and it is not ready for primetime. Actually, I've already started writing a custom (and sort of optimized) DataObject base class. What _really_ interests me is the design pattern(s) that using dataobjects force you to respect. But if possible I'd like to reuse such stable libs as DB_DataObject. Btw, never header of Novell Forge. Looks good. Good luck with Phreez. -- og