Featured Post

Opting classic row modeling or EAV data modeling?


Few of the circumstances are listed below where EAV scores over conventional tables:
·         The data type of individual attributes varies. Like in above example EAV is used because the requirements vary from client to client like some may want an extra address like added to existing address format.
·         The categories of data are numerous, growing or fluctuating, but the number of instances (records/rows) within each category is very small. Here, with conventional modeling, the database’s Entity-Relationship Diagram might have hundreds of tables: the tables that contain thousands/ millions of rows/instances are emphasized visually to the same extent as those with very few rows. The latter are candidates for conversion to an EAV representation.


Other Related Links:
EAV(Entity-Attribute Value) Model


Comments

Related Posts

Scrum Roles (Scrum Master, Product owner, Development Team) and collaboration between each other

Team Roles/Group Roles (Belbin) within the project and Four classes of culture

The bug in the name of the C++ language.

Working with Git Repositories Using GitHub Desktop

Difference in Verification and Validation of requirement? : Requirement Traceability Matrix?