Timeline for How can I model unknown and an unknown number of attributes on an object?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2018 at 0:31 | comment | added | btilly | @BerinLoritsch There are plenty of document databases out there. However I stand by my comment. The overhead of the relational layer is very small. If a document database is going to be massively faster, it has to be at the cost of losing reliability guarantees. | |
| May 30, 2018 at 20:26 | comment | added | Berin Loritsch | @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. | |
| May 30, 2018 at 19:57 | comment | added | btilly | @BerinLoritsch Actually RDBMS systems have better reliable performance than document databases. See percona.com/live/e17/sites/default/files/slides/…. | |
| May 30, 2018 at 17:28 | comment | added | Berin Loritsch | 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. | |
| May 30, 2018 at 17:20 | answer | added | btilly | timeline score: 3 | |
| May 30, 2018 at 17:14 | comment | added | btilly | @DocBrown An EAV is simple to set up, but doesn't perform very well... | |
| May 30, 2018 at 16:01 | comment | added | Doc Brown | 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). | |
| May 30, 2018 at 15:40 | review | First posts | |||
| May 30, 2018 at 18:40 | |||||
| May 30, 2018 at 15:40 | history | asked | DjangoNoobie | CC BY-SA 4.0 |