Home/ Questions/Q 4258292
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T05:37:46+00:00

Say I have an entity that will have many attributes, some I know about

  • 0

Say I have an entity that will have many attributes, some I know about now and others will be user defined. What’s the best way to model this?

1) Do I have a main table and relate it to a secondary name-value pair table? All the attributes go in the secondary EAV table.

  • OR –

2) Do I put the most common attributes (not all users will need them, so I expect a lot of NULL entries) in the main table and have the secondary EAV table for the user defined attributes?

  • OR –

3) Some other approach I have not thought of?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Typically, lots of empty cells are cheap and not worth normalizing away. The only draw back to #2 is if you have a very large number of rows (millions – where performance problems could arise), a very large number of columns (more than about 20 – where it’s just annoying to look at the data), or there are a number of unique constraints on the EAV table.

    With that said, it is now 2011 and it makes sense to use a programming framework with a database abstraction layer these days so that you’re not designing database relationships directly. Something like Django’s Object Relational Mapper allow you to focus on the models themselves and let best practices take care of themselves (95% of the time). This tutorial will help you get started. Django only applies to web development database modeling. For non-web environments, other frameworks will be better.

    • 0