cm0002@lemmy.world to Programmer Humor@programming.dev · 1 day agoGood Morninglemmy.mlimagemessage-square54linkfedilinkarrow-up1755cross-posted to: [email protected]
arrow-up1755imageGood Morninglemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 day agomessage-square54linkfedilinkcross-posted to: [email protected]
minus-squareDerpgon@programming.devlinkfedilinkarrow-up11·1 day agoMysql / Mari can handle it too! Just use BLOB 🤣
minus-squarelime!@feddit.nulinkfedilinkEnglisharrow-up24·1 day agopg can actually query into json fields!
minus-squarelime!@feddit.nulinkfedilinkEnglisharrow-up4·15 hours agooh i didn’t know that. iirc postgres easily beats mongo in json performance which is a bit embarrassing.
minus-squareDerpgon@programming.devlinkfedilinkarrow-up1·12 hours agoHoly, never knew, and never would expect. Postgres truly is king.
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up11·1 day agoAnd you can add indexes on those JSON fields too!
minus-squareTja@programming.devlinkfedilinkarrow-up5·20 hours agoKind of. I hope you don’t like performance…
minus-squareTanoh@lemmy.worldlinkfedilinkarrow-up1·25 minutes 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-up1·9 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-up1·8 hours agoQuite well is very subjective. It’s much slower than columns or specialized databases like MongoDB.
Mysql / Mari can handle it too! Just use BLOB 🤣
pg can actually query into json fields!
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.
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.