Avoid these ORM things like the plague! They seem great in theory, but if you're doing anything serious, they will quickly get in your way. Not to mention all that fancy "ORM" doesn't come without a price. It costs in terms of speed, as well as training. You're much better off to make your custom tools for your particular application. -----Original Message----- From: Alexandru Patranescu [mailto:drealecs@xxxxxxxxx] Sent: Wednesday, December 08, 2010 9:10 PM To: Tommy Pham Cc: PHP Subject: Re: ORM doctrine Doctrine is mature and well I've seen it plenty of times companies using it. Of course it handles multi table joins but I think it's main purpose is not related to users writing joins... It's an ORM, you just read and write objects. Caching is something that must be there and you can read more on wiki: http://en.wikipedia.org/wiki/Doctrine_%28PHP%29 Alex On Thu, Dec 9, 2010 at 5:02 AM, Tommy Pham <tommyhp2@xxxxxxxxx> wrote: > Hi, > > Has anyone used doctrine before? I know Nathan mentioned it in the other > thread but I was wondering how does it handle multi table joins query, > about > its performance and whether it uses any type of caching. > > Thanks, > Tommy > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
