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

  1. Entity
  2. Attrubute
  3. 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.

Related posts:

The following two tabs change content below.

Chandra Shekhar

GCP Architect
Chandra Shekhar Pandey is Google certified Cloud engineer, I am Magento2 Trained developer. Having huge experience in designing cloud solution. I have around 12 years of experience with world enterprise IT companies and fortune 500 clients. During my architecture design I am always caring about high availability, fast performance and resilient system. From the programmer background I have huge experience in LAMP stack as well. Throughout my carrier I have worked on Retail, E-Learning, Video... Read More about Chandra Shekhar

Latest posts by Chandra Shekhar (see all)