Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 3
    If attributes have to be configured by an end user, EAV like your key/value table is probably your best choice. Just consider to add also some metadata (for example, for describing the data type of each value). Commented May 30, 2018 at 16:01
  • @DocBrown An EAV is simple to set up, but doesn't perform very well... Commented May 30, 2018 at 17:14
  • Sounds like a document database would be ideal for this situation, particularly since they are more efficient at searching than normal RDBMS with JSON field support bolted on. Commented May 30, 2018 at 17:28
  • @BerinLoritsch Actually RDBMS systems have better reliable performance than document databases. See percona.com/live/e17/sites/default/files/slides/…. Commented May 30, 2018 at 19:57
  • @btilly, I'll have to check that out when I get home. I'm having difficulty downloading the PDF at work. However, I will say that MongoDB (mentioned in the file name) is the last document database I reach for. Might not be a fair comparison. Commented May 30, 2018 at 20:26