Indeed, it 's al about trade-offs. When using something like doctrine, you are effectively choosing for speed in development while sacrificing some performance of your application. If you must choose an ORM (which I often do myself), then choose doctrine. Not for speed or performance reasons, but because doctrine keeps you, as a developer, closer to the database layer. The querying closely resembles SQL and it is easier to optimize and make joins than with Propel.
James On Jul 4, 2:33 pm, Sherif <[email protected]> wrote: > Agree with James. At some stage you need to weigh up the value of ORM > vs performance if you hit a performance issue. Nothing beats you going > straight to the databsae for performance.. but you loose the whole ORM > side of things.. its all about trade-offs! > > On Jul 4, 7:49 pm, Cyrille37 <[email protected]> wrote: > > > Thanks James and John for those tips ! > > > I think I'll use the ORM for backend, and the frontend will contains > > custom wild stuff ;-) > > > Regards > > Cyrille --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
