ORM (Object-relational mapping) is a mapping of objects in memory and relational data, and in Java, Hibernate can be understood to be an object operation, but most of the PHP ORM is chained (in fact, the string is spliced), the last operation will execute the statement, It's equivalent to splicing a SQL in the code, so why is it called an ORM object-relational mapping object, and where does it behave?
Reply content:
ORM (Object-relational mapping) is a mapping of objects in memory and relational data, and in Java, Hibernate can be understood to be an object operation, but most of the PHP ORM is chained (in fact, the string is spliced), the last operation will execute the statement, It's equivalent to splicing a SQL in the code, so why is it called an ORM object-relational mapping object, and where does it behave?
Your question is a little too vague, Java you point out Hibernate, but the problem is that PHP, first of all, a Java framework, one is a language.
Business:
What you call a chained operation is just to make it easier to finally build SQL,
class Foobar { public function query() { return $this }}
In this, query () returns to the object itself, which allows for chained operations, but does this have a hair-to-orm relationship? Object foobar, corresponding data table Foobar, isn't that an ORM? What does it matter how the middle is achieved?
The main or the main view of the data mixed with Dbal/dao and ORM
Roughly speaking, the "stitching query" is dbal, which maps data records to objects that are ORM