Understanding magento data storage
Understanding magento database structure is really a complex target in itself. But once we are able to understand it, we found that magento database is very tightly coupled and very normalized. It is synchronized such that its not easy to write an easy query to find any information from db.
The reason behind it is that Magento uses EAV Model of database in which for evary information it breaks data in three separate section
- Entity
- Attrubute
- Value
To implement the EAV Model . Magento uses eav_entity_type and eav_attribute . I am demonstrating how magento store customer information . Core tables are started with prefix eav_
For example if we take customer information .
From the image given above you can see. For every new entity we create magento create a new entry in eav_entity_type table and this entity_type_id is used to linked with eav_attribute table.Because we are taking the example of customer entity the a new table customer_entity is created and their attribute will be stored in customer_eav_attribute and based on the data type actual values will be stored in the tables which are shown in blue above.
I hope you understand it…….. Otherwise you can contact me via comment i will reply them.
Chandra Shekhar
Latest posts by Chandra Shekhar (see all)
- Best practices for micro service design - January 23, 2022
- Spring Boot - January 23, 2022
- Java - January 23, 2022
Recent Comments