cm0002@lemmy.world to Programmer Humor@programming.dev · 5 days agoGood Morninglemmy.mlimagemessage-square56fedilinkarrow-up1815arrow-down15cross-posted to: programmerhumor@lemmy.ml
arrow-up1810arrow-down1imageGood Morninglemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 5 days agomessage-square56fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up14·4 days agoAnd you can add indexes on those JSON fields too!
minus-squareTja@programming.devlinkfedilinkarrow-up7·4 days agoKind of. I hope you don’t like performance…
minus-squarejubilationtcornpone@sh.itjust.workslinkfedilinkarrow-up2·4 days 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·4 days agoQuite well is very subjective. It’s much slower than columns or specialized databases like MongoDB.
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up1·3 days 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!
And you can add indexes on those JSON fields too!
Kind of. I hope you don’t like performance…
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.
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!