CODEWITHSUNDEEP
phpcodeigniteractiverecordorm
Industrial
Industrial

Reputation: 42778

Advantage with using "defined" ORM:s in PHP?

After working a while with Codeigniter, I am totally in love with the ActiveRecord way of writing mySQL queries. Now, when working on another non-codeigniter project I've been recommended to use an ORM to handle the DB mapping which sounds great, but after looking into Propel & Doctrine, I have become quite afraid of the additional configuration files containing the database structure, more or less.

Why does these ORM:s define the database structure and what advantage has it over an non-defined ORM like the one that's bundled with codeIgniter?

Upvotes: 3

Views: 196

Answers (1)

zeroSkillz
zeroSkillz

Reputation: 1468

FYI, there was a thread about this a while ago. The gist of it is that ORMs (ActiveRecord is an common ORM pattern) help enable database independence and quicker access to common queries. Downside is that ORMs are "heavier" than straight SQL. For most apps, 90% of your data access is pretty standardized so ORMs help with time to market.

ORM and Active Record Pattern in PHP?

Upvotes: 2

Related Questions