However, if you use this structure to add a new attribute for the product, you have to change much database and code (add more columns or create a new table to save attributes).įurthermore, there are unnecessary attributes you don’t need to enter data for a product, causing a larger number of columns without data that is no need to apply to the current product. In case the store owner widens the business scope by selling more products and each of them includes specific attributes (color, size, height,…), this simple structure still meets usage demand and data organization to implement necessary queries. It doesn’t matter at all if the store owner just sells one product containing some attributes. All products are stored in the product table. Without changing the basic database structure, developers can add properties to any entity (product, category, customer, order, etc.).Īs can be seen from the above image, this is the most simple and less flexible data structure between catalog and products of a store (Flat model). The EAV database structure is employed because it is substantially more scalable than a normalised database structure. This article mainly concentrates on explaining seven concerns as below: 1. Today, we will reveal a complete tutorial of the Magento 2 Entity-Attribute-Value model (Magento EAV), which is essential for every developer to build products or do projects at a higher customization level. ![]() ![]() Now, it’s so glad to come back and continue providing all of you with more useful Magento 2 tutorials from now on. Magento 2 EAV Model is a valuable feature.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |