JPDev@programming.dev to Programmer Humor@programming.dev · 2 months agoJSON Query Languageprogramming.devimagemessage-square48fedilinkarrow-up1857arrow-down119
arrow-up1838arrow-down1imageJSON Query Languageprogramming.devJPDev@programming.dev to Programmer Humor@programming.dev · 2 months agomessage-square48fedilink
minus-squarejaybone@lemmy.worldlinkfedilinkarrow-up38arrow-down1·2 months agoBoth Oracle and Postgres have pretty good support for json in SQL.
minus-squarewhere_am_i@sh.itjust.workslinkfedilinkarrow-up18arrow-down1·2 months agoand the plane in the picture is perfectly capable of transporting a plane. What’s your point?
minus-squarexmunk@sh.itjust.workslinkfedilinkarrow-up19·2 months agoJSON in the DB isn’t an antipattern. It is frequently used in absolutely terrible designs but it is not itself a bad thing. I’m a data architect and I approve this message.
minus-squarelengau@midwest.sociallinkfedilinkarrow-up9arrow-down1·2 months agoCarrying the body of a smaller plane in a larger plane isn’t an antipattern either. Airbus does this between body assembly and attaching the wings.
minus-square✺roguetrick✺@lemmy.worldlinkfedilinkarrow-up6arrow-down1·2 months agoI think plane people call it a fusilage, because they’re weird and like French.
minus-squareEnoril@jlai.lulinkfedilinkarrow-up9·2 months agoIt’s “fuselage”. It’s called like that because of it came from the word “forme fuselé” (Tapered shape) and it’s a french word mainly because we created it in 1908. You’re welcome :-)
minus-squaremeliaesc@lemmy.worldlinkfedilinkarrow-up2arrow-down3·2 months agoWhy not use nosql if your important data is stored in JSON? You can still do all your fancy little joins and whatnot.
minus-squarefrezik@midwest.sociallinkfedilinkarrow-up4·2 months agoTurn it inside out. Why not use a RDBMS with a NoSQL bit added on the side?
minus-squarexmunk@sh.itjust.workslinkfedilinkarrow-up3·2 months agoSpecifically so you get mature transactional guarantees, indices and constraints that let app developers trust your db.
Both Oracle and Postgres have pretty good support for json in SQL.
and the plane in the picture is perfectly capable of transporting a plane. What’s your point?
JSON in the DB isn’t an antipattern. It is frequently used in absolutely terrible designs but it is not itself a bad thing.
I’m a data architect and I approve this message.
Carrying the body of a smaller plane in a larger plane isn’t an antipattern either. Airbus does this between body assembly and attaching the wings.
I think plane people call it a fusilage, because they’re weird and like French.
It’s “fuselage”.
It’s called like that because of it came from the word “forme fuselé” (Tapered shape) and it’s a french word mainly because we created it in 1908.
You’re welcome :-)
Why not use nosql if your important data is stored in JSON? You can still do all your fancy little joins and whatnot.
Turn it inside out. Why not use a RDBMS with a NoSQL bit added on the side?
Specifically so you get mature transactional guarantees, indices and constraints that let app developers trust your db.