JSON Query LanguageJPDev@programming.dev to Programmer Humor@programming.dev – 819 points – 2 months ago47Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentand 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.
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.
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.
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 :-)
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 :-)
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.
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.
Specifically so you get mature transactional guarantees, indices and constraints that let app developers trust your db.
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.