Hey, I dont know much about the different PHP abstraction layers, but what I know is that they slow the system down. For small scale application you might not really feel it but if you go on larger applications or even to the enterprise level you should write you data access layer for a specific database (also it is very uncommon that a client/project would change the DB type frequently or often). The same applies to templating systems like Smarty, they are very convenient but at a certain point they do slow down the process of serving a page. Better is to use a templating system like the one incorporated in Symfony (which is purely PHP without parsing etc. etc.).
Hope that helped somehow Cheers, Mozzy From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Al-Faisal El-Dajani Sent: Tuesday, October 16, 2007 1:31 PM To: Jordan PHP User Group Mailing list Subject: [JoPHP] Are database abstraction layers worth it? Hello all, I've been searching lately for a database abstraction layer to use with a new project i'm about to start. I tried building my own, and using pear's MDB2, and hated both. During my search, i came along many forums that were discussing if it is worth using one in the first place (of course, templating engines were dragged into the discussion as well). So my question is, is it worth using a database abstraction layer and a templating engine? if so which do you recommend? if not why? Cheers, -- Al-Faisal El-Dajani Phone: +962-7-79 73 70 50 P.O Box: 140056 11814 Amman, Jordan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Jordan PHP Users Group" 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/JoPHP http://Jolug.org/ -~----------~----~----~----~------~----~------~--~---
