cm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agoGood Morninglemmy.mlimagemessage-square56fedilinkarrow-up1800arrow-down15
arrow-up1795arrow-down1imageGood Morninglemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agomessage-square56fedilink
minus-squarelime!@feddit.nulinkfedilinkEnglisharrow-up27·2 days agopg can actually query into json fields!
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up13·2 days agoAnd you can add indexes on those JSON fields too!
minus-squareTja@programming.devlinkfedilinkarrow-up6·2 days agoKind of. I hope you don’t like performance…
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up1·24 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·1 day 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·1 day agoQuite well is very subjective. It’s much slower than columns or specialized databases like MongoDB.
minus-squarelime!@feddit.nulinkfedilinkEnglisharrow-up4·2 days agooh i didn’t know that. iirc postgres easily beats mongo in json performance which is a bit embarrassing.
minus-squareDerpgon@programming.devlinkfedilinkarrow-up1·1 day agoHoly, never knew, and never would expect. Postgres truly is king.
pg can actually query into json fields!
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.
Mysql can too, slow af tho.
oh i didn’t know that. iirc postgres easily beats mongo in json performance which is a bit embarrassing.
Holy, never knew, and never would expect. Postgres truly is king.