longyi c9405dd336 vendor 5 lat temu
..
Db c9405dd336 vendor 5 lat temu
Observer c9405dd336 vendor 5 lat temu
Operation c9405dd336 vendor 5 lat temu
Sequence c9405dd336 vendor 5 lat temu
Test c9405dd336 vendor 5 lat temu
AbstractModelHydrator.php c9405dd336 vendor 5 lat temu
CallbackHandler.php c9405dd336 vendor 5 lat temu
CompositeMapper.php c9405dd336 vendor 5 lat temu
EntityManager.php c9405dd336 vendor 5 lat temu
EntityMetadata.php c9405dd336 vendor 5 lat temu
EntityMetadataInterface.php c9405dd336 vendor 5 lat temu
EventManager.php c9405dd336 vendor 5 lat temu
Hydrator.php c9405dd336 vendor 5 lat temu
HydratorInterface.php c9405dd336 vendor 5 lat temu
HydratorPool.php c9405dd336 vendor 5 lat temu
Mapper.php c9405dd336 vendor 5 lat temu
MapperInterface.php c9405dd336 vendor 5 lat temu
MapperPool.php c9405dd336 vendor 5 lat temu
MetadataPool.php c9405dd336 vendor 5 lat temu
OperationInterface.php c9405dd336 vendor 5 lat temu
OperationPool.php c9405dd336 vendor 5 lat temu
README.md c9405dd336 vendor 5 lat temu
TypeResolver.php c9405dd336 vendor 5 lat temu

README.md

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.