Comments on: Doctrine – PHP Object Relational Mapper http://www.gen-x-design.com/archives/doctrine-php-object-relational-mapper/ Just another WordPress weblog Thu, 17 Mar 2011 15:00:42 -0700 http://wordpress.org/?v=2.8 hourly 1 By: hafij http://www.gen-x-design.com/archives/doctrine-php-object-relational-mapper/#comment-2193 hafij Tue, 03 Aug 2010 14:14:16 +0000 http://www.gen-x-design.com/?p=288#comment-2193 Here I must share something. I have worked on many several frameworks and many different orm. But there is no such thing best out of those. As you rightly pointed out that a framework with huge load is not good at all. In my project that I am working on, the total number of users are more than 50 thousands and the total number of images are more than 2 milion. Given this situation you have to pick very lightweight orm system. The conditions are, 1. No foreign key relationship. (Your code must handle it). 2. Standalone table is just a standalone class. 3. You can have up to 2nd or 3rd order of normalizaion for you database. (Less join means more speed, less constraint means less overhead). 4. Never load associate object all together what cakephp does. 5. Its really a pain to have xml or yml file to maintain database stuff. 6. Doctrine is not simple at all. Now think about any mvc framework. Any framework must give a standard but without magical stuff. Such as validators, helpers etc. This is really bad if you think about a site with huge number of request every time. Go and visit http://phpwebpad.hafij.com. Here I must share something. I have worked on many several frameworks and many different orm. But there is no such thing best out of those. As you rightly pointed out that a framework with huge load is not good at all. In my project that I am working on, the total number of users are more than 50 thousands and the total number of images are more than 2 milion. Given this situation you have to pick very lightweight orm system. The conditions are,

1. No foreign key relationship. (Your code must handle it).
2. Standalone table is just a standalone class.
3. You can have up to 2nd or 3rd order of normalizaion for you database. (Less join means more speed, less constraint means less overhead).
4. Never load associate object all together what cakephp does.
5. Its really a pain to have xml or yml file to maintain database stuff.
6. Doctrine is not simple at all.

Now think about any mvc framework. Any framework must give a standard but without magical stuff. Such as validators, helpers etc. This is really bad if you think about a site with huge number of request every time. Go and visit http://phpwebpad.hafij.com.

]]> By: Faizan http://www.gen-x-design.com/archives/doctrine-php-object-relational-mapper/#comment-2017 Faizan Sun, 17 Jan 2010 05:44:02 +0000 http://www.gen-x-design.com/?p=288#comment-2017 I'm now using doctrine for a year now. I've used it with symfony and codeigniter, and it is best PHP ORM I’m now using doctrine for a year now. I’ve used it with symfony and codeigniter, and it is best PHP ORM

]]> By: Phillip Harrington http://www.gen-x-design.com/archives/doctrine-php-object-relational-mapper/#comment-1384 Phillip Harrington Thu, 21 May 2009 16:42:59 +0000 http://www.gen-x-design.com/?p=288#comment-1384 I too have been in the same spot - not wanting to use a huge framework every time - but not wanting to write my own. I'll definitely check out doctrine. Thanks for the tip. I too have been in the same spot – not wanting to use a huge framework every time – but not wanting to write my own. I’ll definitely check out doctrine. Thanks for the tip.

]]>