The advantage of using "specific" ORM: s in PHP?

After working with Codeigniter, I am completely in love with the ActiveRecord method for writing mySQL queries. Now, when I was working on a project other than the cognitive one, I was recommended to use ORM to handle DB matching, which sounds great, but after learning Propel and Doctrine, I was very afraid of the additional configuration files containing the database structure, more or less.

Why do these ORM: s define the database structure and what advantage does it have over an undefined ORM, like the one associated with codeIgniter?

+3
source share
1 answer

FYI, . , ORM (ActiveRecord - ORM) . , ORM "", SQL. 90% , ORM .

ORM PHP?

+2

Source: https://habr.com/ru/post/1790834/


All Articles