▲ 818 ▼ Good Morning (lemmy.ml) submitted 1 year ago by cm0002@lemmy.world to c/programmer_humor@programming.dev 56 comments fedilink hide all child comments
[–] lime@feddit.nu 27 points 1 year ago (8 children) pg can actually query into json fields! permalink fedilink source parent hideshow 8 child comments replies: [–] Tanoh@lemmy.world 14 points 1 year ago (4 children) And you can add indexes on those JSON fields too! permalink fedilink source parent hideshow 4 child comments replies: [–] Tja@programming.dev 7 points 1 year ago (3 children) Kind of. I hope you don't like performance... permalink fedilink source parent hideshow 3 child comments replies: [–] jubilationtcornpone@sh.itjust.works 2 points 1 year ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] Tja@programming.dev 2 points 1 year ago Quite well is very subjective. It's much slower than columns or specialized databases like MongoDB. permalink fedilink source parent [–] Tanoh@lemmy.world 1 point 1 year ago 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! permalink fedilink source parent [–] derpgon@programming.dev 3 points 1 year ago (2 children) Mysql can too, slow af tho. permalink fedilink source parent hideshow 2 child comments replies: [–] lime@feddit.nu 4 points 1 year ago (1 child) oh i didn't know that. iirc postgres easily beats mongo in json performance which is a bit embarrassing. permalink fedilink source parent hideshow 1 child comment replies: [–] derpgon@programming.dev 1 point 1 year ago Holy, never knew, and never would expect. Postgres truly is king. permalink fedilink source parent
[–] Tanoh@lemmy.world 14 points 1 year ago (4 children) And you can add indexes on those JSON fields too! permalink fedilink source parent hideshow 4 child comments replies: [–] Tja@programming.dev 7 points 1 year ago (3 children) Kind of. I hope you don't like performance... permalink fedilink source parent hideshow 3 child comments replies: [–] jubilationtcornpone@sh.itjust.works 2 points 1 year ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] Tja@programming.dev 2 points 1 year ago Quite well is very subjective. It's much slower than columns or specialized databases like MongoDB. permalink fedilink source parent [–] Tanoh@lemmy.world 1 point 1 year ago 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! permalink fedilink source parent
[–] Tja@programming.dev 7 points 1 year ago (3 children) Kind of. I hope you don't like performance... permalink fedilink source parent hideshow 3 child comments replies: [–] jubilationtcornpone@sh.itjust.works 2 points 1 year ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] Tja@programming.dev 2 points 1 year ago Quite well is very subjective. It's much slower than columns or specialized databases like MongoDB. permalink fedilink source parent [–] Tanoh@lemmy.world 1 point 1 year ago 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! permalink fedilink source parent
[–] jubilationtcornpone@sh.itjust.works 2 points 1 year ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] Tja@programming.dev 2 points 1 year ago Quite well is very subjective. It's much slower than columns or specialized databases like MongoDB. permalink fedilink source parent
[–] Tja@programming.dev 2 points 1 year ago Quite well is very subjective. It's much slower than columns or specialized databases like MongoDB. permalink fedilink source parent
[–] Tanoh@lemmy.world 1 point 1 year ago 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! permalink fedilink source parent
[–] derpgon@programming.dev 3 points 1 year ago (2 children) Mysql can too, slow af tho. permalink fedilink source parent hideshow 2 child comments replies: [–] lime@feddit.nu 4 points 1 year ago (1 child) oh i didn't know that. iirc postgres easily beats mongo in json performance which is a bit embarrassing. permalink fedilink source parent hideshow 1 child comment replies: [–] derpgon@programming.dev 1 point 1 year ago Holy, never knew, and never would expect. Postgres truly is king. permalink fedilink source parent
[–] lime@feddit.nu 4 points 1 year ago (1 child) oh i didn't know that. iirc postgres easily beats mongo in json performance which is a bit embarrassing. permalink fedilink source parent hideshow 1 child comment replies: [–] derpgon@programming.dev 1 point 1 year ago Holy, never knew, and never would expect. Postgres truly is king. permalink fedilink source parent
[–] derpgon@programming.dev 1 point 1 year ago Holy, never knew, and never would expect. Postgres truly is king. permalink fedilink source parent
