Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
 
 
 
 
 
 
Florian Eisenmenger 41ccc32b5d checkin 2 lat temu
..
Db checkin 2 lat temu
Observer checkin 2 lat temu
Operation checkin 2 lat temu
Sequence checkin 2 lat temu
Test/Unit checkin 2 lat temu
AbstractModelHydrator.php checkin 2 lat temu
CallbackHandler.php checkin 2 lat temu
CompositeMapper.php checkin 2 lat temu
EntityManager.php checkin 2 lat temu
EntityMetadata.php checkin 2 lat temu
EntityMetadataInterface.php checkin 2 lat temu
EventManager.php checkin 2 lat temu
Hydrator.php checkin 2 lat temu
HydratorInterface.php checkin 2 lat temu
HydratorPool.php checkin 2 lat temu
Mapper.php checkin 2 lat temu
MapperInterface.php checkin 2 lat temu
MapperPool.php checkin 2 lat temu
MetadataPool.php checkin 2 lat temu
OperationInterface.php checkin 2 lat temu
OperationPool.php checkin 2 lat temu
README.md checkin 2 lat temu
TypeResolver.php checkin 2 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.