Should I use my ORM objects as an object of my domain?

My ORM creates objects that reflect the structure of the database table. These objects are extensible, so I can add new properties and methods. These objects do not contain any conservation logic, so I assume that they are persistent in ignorance.

Should I use this object as objects of my domain or do I need to create new objects for the model of the main domains?

As a pro to create a new object, I would think that if you change the database table, it will not break the application.

As a console for creating a new object, I would consider additional matching and greater complexity in the application.

+3
source share
2

, . , , , , db, , , .

, db , , .

+1

, ORM , , , , , ORM , .

, . , , .

+5

All Articles