longyi
c9405dd336
vendor
|
5 years ago | |
|---|---|---|
| .. | ||
| Db | 5 years ago | |
| Observer | 5 years ago | |
| Operation | 5 years ago | |
| Sequence | 5 years ago | |
| Test | 5 years ago | |
| AbstractModelHydrator.php | 5 years ago | |
| CallbackHandler.php | 5 years ago | |
| CompositeMapper.php | 5 years ago | |
| EntityManager.php | 5 years ago | |
| EntityMetadata.php | 5 years ago | |
| EntityMetadataInterface.php | 5 years ago | |
| EventManager.php | 5 years ago | |
| Hydrator.php | 5 years ago | |
| HydratorInterface.php | 5 years ago | |
| HydratorPool.php | 5 years ago | |
| Mapper.php | 5 years ago | |
| MapperInterface.php | 5 years ago | |
| MapperPool.php | 5 years ago | |
| MetadataPool.php | 5 years ago | |
| OperationInterface.php | 5 years ago | |
| OperationPool.php | 5 years ago | |
| README.md | 5 years ago | |
| TypeResolver.php | 5 years ago | |
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.