|
Apache/2.4.41 (Ubuntu) Linux vmi616275.contaboserver.net 5.4.0-84-generic #94-Ubuntu SMP Thu Aug 26 20:27:37 UTC 2021 x86_64 uid=33(www-data) gid=33(www-data) groups=33(www-data) server ip : 62.171.164.128 | your ip : 127.0.0.1 safemode OFF > / home / dev2.destoffenstraat.com / vendor / magento / framework / EntityManager / |
Filename | /home/dev2.destoffenstraat.com/vendor/magento/framework/EntityManager/README.md |
Size | 967 |
Permission | rw-r--r-- |
Owner | root : root |
Create time | 17-Aug-2025 10:26 |
Last modified | 07-Jan-2021 21:08 |
Last accessed | 21-Aug-2025 18:30 |
Actions | edit | rename | delete | download (gzip) |
View | text | code | image |
# EntityManager
**EntityManager** library contains functionality for entity persistence layer.
EntityManager supports persistence of basic entity attributes as well as extension and custom attributes
added by 3rd party developers for the purpose of extending default entity behavior.
It's not recommended to use EntityManager and its infrastructure for your entity persistence.
In the nearest future new Persistence Entity Manager would be released which will cover all the requirements for
persistence layer along with Query API as performance efficient APIs for Read scenarios.
Currently, it's recommended to use Resource Model infrastructure and make a successor of
Magento\Framework\Model\ResourceModel\Db\AbstractDb class or successor of
Magento\Eav\Model\Entity\AbstractEntity if EAV attributes support needed.
For filtering operations, it's recommended to use successor of
Magento\Framework\Model\ResourceModel\Db\Collection\AbstractCollection class.
**EntityManager** library contains functionality for entity persistence layer.
EntityManager supports persistence of basic entity attributes as well as extension and custom attributes
added by 3rd party developers for the purpose of extending default entity behavior.
It's not recommended to use EntityManager and its infrastructure for your entity persistence.
In the nearest future new Persistence Entity Manager would be released which will cover all the requirements for
persistence layer along with Query API as performance efficient APIs for Read scenarios.
Currently, it's recommended to use Resource Model infrastructure and make a successor of
Magento\Framework\Model\ResourceModel\Db\AbstractDb class or successor of
Magento\Eav\Model\Entity\AbstractEntity if EAV attributes support needed.
For filtering operations, it's recommended to use successor of
Magento\Framework\Model\ResourceModel\Db\Collection\AbstractCollection class.