File tree Expand file tree Collapse file tree 2 files changed +26
-3
lines changed
lib/internal/Magento/Framework/EntityManager Expand file tree Collapse file tree 2 files changed +26
-3
lines changed Original file line number Diff line number Diff line change 12
12
use Magento \Framework \EntityManager \Operation \UpdateInterface ;
13
13
14
14
/**
15
- * Class EntityManager
15
+ * It's not recommended to use EntityManager and its infrastructure for your entities persistence.
16
+ * In the nearest future new Persistence Entity Manager would be released which will cover all the requirements for
17
+ * persistence layer along with Query API as performance efficient APIs for Read scenarios.
18
+ *
19
+ * Currently, it's recommended to use Resource Model infrastructure and make a successor of
20
+ * Magento\Framework\Model\ResourceModel\Db\AbstractDb class or successor of
21
+ * Magento\Eav\Model\Entity\AbstractEntity if EAV attributes support needed.
22
+ *
23
+ * For filtering operations, it's recommended to use successor of
24
+ * Magento\Framework\Model\ResourceModel\Db\Collection\AbstractCollection class.
25
+ *
26
+ * @SuppressWarnings(PHPMD.CouplingBetweenObjects)
16
27
*/
17
28
class EntityManager
18
29
{
Original file line number Diff line number Diff line change 1
1
# EntityManager
2
2
3
- ** EntityManager** library contains functionality for management entity instances.
4
- It includes read and write operations as for entity as for their attributes and extensions.
3
+ ** EntityManager** library contains functionality for entity persistence layer.
4
+ EntityManager supports persistence of basic entity attributes as well as extension and custom attributes
5
+ added by 3rd party developers for the purpose of extending default entity behavior.
6
+
7
+ It's not recommended to use EntityManager and its infrastructure for your entity persistence.
8
+ In the nearest future new Persistence Entity Manager would be released which will cover all the requirements for
9
+ persistence layer along with Query API as performance efficient APIs for Read scenarios.
10
+
11
+ Currently, it's recommended to use Resource Model infrastructure and make a successor of
12
+ Magento\Framework\Model\ResourceModel\Db\AbstractDb class or successor of
13
+ Magento\Eav\Model\Entity\AbstractEntity if EAV attributes support needed.
14
+
15
+ For filtering operations, it's recommended to use successor of
16
+ Magento\Framework\Model\ResourceModel\Db\Collection\AbstractCollection class.
You can’t perform that action at this time.
0 commit comments