cm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agoGood Morningimagemessage-square56fedilinkarrow-up1776arrow-down15cross-posted to: programmerhumor@lemmy.ml
arrow-up1771arrow-down1imageGood Morningcm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agomessage-square56fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up13·1 day agoAnd you can add indexes on those JSON fields too!
minus-squareTja@programming.devlinkfedilinkarrow-up6·1 day agoKind of. I hope you don’t like performance…
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up1·6 hours agoSure, if you use a field often it is most likely better to extract it into a column with auto-updates from the JSON data. But you have to tune it and see what is best for your use case. Just saying that you can add indexes to JSON fields as well!
minus-squarejubilationtcornpone@sh.itjust.workslinkfedilinkarrow-up2·15 hours agoThe performance is actually not bad. You’re far better off using conventional columns but in the one off cases where you have to store queryable JSON data, it actually performs quite well.
minus-squareTja@programming.devlinkfedilinkarrow-up2·14 hours agoQuite well is very subjective. It’s much slower than columns or specialized databases like MongoDB.
And you can add indexes on those JSON fields too!
Kind of. I hope you don’t like performance…
Sure, if you use a field often it is most likely better to extract it into a column with auto-updates from the JSON data.
But you have to tune it and see what is best for your use case. Just saying that you can add indexes to JSON fields as well!
The performance is actually not bad. You’re far better off using conventional columns but in the one off cases where you have to store queryable JSON data, it actually performs quite well.
Quite well is very subjective. It’s much slower than columns or specialized databases like MongoDB.