Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
 
 
 
 
 
 
Florian Eisenmenger 41ccc32b5d checkin 2 anos atrás
..
Db checkin 2 anos atrás
Observer checkin 2 anos atrás
Operation checkin 2 anos atrás
Sequence checkin 2 anos atrás
Test/Unit checkin 2 anos atrás
AbstractModelHydrator.php checkin 2 anos atrás
CallbackHandler.php checkin 2 anos atrás
CompositeMapper.php checkin 2 anos atrás
EntityManager.php checkin 2 anos atrás
EntityMetadata.php checkin 2 anos atrás
EntityMetadataInterface.php checkin 2 anos atrás
EventManager.php checkin 2 anos atrás
Hydrator.php checkin 2 anos atrás
HydratorInterface.php checkin 2 anos atrás
HydratorPool.php checkin 2 anos atrás
Mapper.php checkin 2 anos atrás
MapperInterface.php checkin 2 anos atrás
MapperPool.php checkin 2 anos atrás
MetadataPool.php checkin 2 anos atrás
OperationInterface.php checkin 2 anos atrás
OperationPool.php checkin 2 anos atrás
README.md checkin 2 anos atrás
TypeResolver.php checkin 2 anos atrás

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.