Questions tagged [eav]

Questions about Magento's Entity Attribute Value (EAV) implementation

Magento uses EAV database table structure for products, categories and customers.

In EAV, data is stored across several tables:

  • Entity table (for example the products with basic information such as sku and URL key)
  • Attribute table (for example all possible product attributes)
  • Value tables (for example all integer values for product attributes)

A value references an attribute and an entity.

This structure allows flexibility with attributes without adding columns to the entity table itself

The downside is slow select queries with many joins. This is why Magento introduced indexes.

366 questions
1
vote
2 answers

How to understand EAV-related PHP-Code

By seeing Magento wonderful functionality I have seen interested on it and learned Magento. Previously i worked on dotnet. In Magento i have learned the flow and its structure. Now i am struck with understanding PHP code and Magento built in…
prasad maganti
  • 912
  • 2
  • 17
  • 36
1
vote
0 answers

Invalid entity_type specified: opco_planner_theme

I try to create EAV planner module. I am getting this error "Invalid entity_type specified: opco_planner_theme". All i want to understand why. class Opco_Planner_Model_Resource_Theme extends Mage_Eav_Model_Entity_Abstract { /** * Resource…
0
votes
1 answer

Following EAV in my Modules

Is it necessary to follow EAV with the models I create for my modules? If not always, when should I and when shouldn't I?
user2045
  • 831
  • 3
  • 16
  • 29