Timeline for Given that they require schema modification locks, why are sparse columns considered an alternative to EAV?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 21 at 12:32 | history | suggested | CommunityBot | CC BY-SA 4.0 |
Just one other notable limitation
|
| Oct 21 at 10:28 | review | Suggested edits | |||
| S Oct 21 at 12:32 | |||||
| Oct 20 at 22:32 | history | edited | J.D. | CC BY-SA 4.0 |
added 516 characters in body
|
| Oct 20 at 20:50 | comment | added | J.D. | @ErikReasonableRatesDarling That's fair. I have no input on Sparse columns, as I have no experience with them. I hope my answer doesn't convey any input on them either other than I'm not aware of any special reasons they help with schema modification locks (so I wouldn't particularly choose to use them for this kind of problem). | |
| Oct 20 at 16:30 | comment | added | Erik Reasonable Rates Darling | My biggest gripes with Sparse columns are that you can't compress any index they're a part of, and changing them is a real process. I don't see anything wrong with your answer for, like, any other column type, but Sparse columns are particularly stupid. | |
| Oct 20 at 1:11 | history | answered | J.D. | CC BY-SA 4.0 |