Timeline for Which is better for long term database scalability: adding columns or having key/value store
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2015 at 15:42 | comment | added | Rick James | It's a tradeoff. If you make everything searchable, you get thousand-column tables or 20-way JOINs, either of which is a really bad idea. In my experience (sorry, no references to back it up), EAV is a bad way to go, especially if you expect to have millions of Entities. | |
| May 17, 2012 at 22:51 | comment | added | valentinas | If I could choose another platform (not standart MySQL/TSQL), then I would probably go with some document database, ravenDB, google App Engine or similar, but that's not the case. As for plan A: do you have any references that would confirm what you're saying? For me this sounds like a really bad practice - the data that I will have would probably fall to nvarchar(100) type and placing that in blob (and loosing ability to query over it) sounds like a really bad idea. | |
| May 17, 2012 at 22:28 | history | answered | Rick James | CC BY-SA 3.0 |