cm0002@lemmy.world to Programmer Humor@programming.dev · 1 个月前Good Morninglemmy.mlimagemessage-square56linkfedilinkarrow-up1823arrow-down15
arrow-up1818arrow-down1imageGood Morninglemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 个月前message-square56linkfedilink
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up14·1 个月前And you can add indexes on those JSON fields too!
minus-squareTja@programming.devlinkfedilinkarrow-up7·1 个月前Kind of. I hope you don’t like performance…
minus-squarejubilationtcornpone@sh.itjust.workslinkfedilinkarrow-up2·1 个月前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.
minus-squareTja@programming.devlinkfedilinkarrow-up2·1 个月前Quite well is very subjective. It’s much slower than columns or specialized databases like MongoDB.
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up1·1 个月前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!
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!