2 ms·
It works until you realize some of these usages would've been better as individual key/value rows. For example, if you want to store settings as JSON, you firs
by ramon156 11mo ago
It works until you realize some of these usages would've been better as individual key/value rows.
For example, if you want to store settings as JSON, you first have to parse it through e.g. Zod, hope that it isn't failing due to schema changes (or write migrations and hope that succeeds).
When a simple key/value row just works fine, and you can even do partial fetches / updates
- mickeyp 11mo agoEAV data models are kinda cursed in their own right, too, though.
- jelder 11mo agoThe necessity of using a JSON column was outside of my control, but Zod etc. are absolutely required, I think, in most projects. I wrote more about that here: https://www.jacobelder.com/2025/01/31/where-shift-left-fails-type-theater.html https://www.jacobelder.com/2025/01/31/where-shift-left-fails...