@cm0002@lemmy.world to Programmer Humor@programming.dev • 1 month agoGood Morninglemmy.mlimagemessage-square56fedilinkarrow-up1820arrow-down15cross-posted to: programmerhumor@lemmy.ml
arrow-up1815arrow-down1imageGood Morninglemmy.ml@cm0002@lemmy.world to Programmer Humor@programming.dev • 1 month agomessage-square56fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-square@Tanoh@lemmy.worldlinkfedilink14•1 month agoAnd you can add indexes on those JSON fields too!
minus-square@jubilationtcornpone@sh.itjust.workslinkfedilink2•1 month 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-square@Tja@programming.devlinkfedilink2•1 month agoQuite well is very subjective. It’s much slower than columns or specialized databases like MongoDB.
minus-square@Tanoh@lemmy.worldlinkfedilink1•1 month 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!