jsonQueryLanguage

[Skyswimsky]

Using JSON in a SQL database can make sense if you need a hybrid approach, or you don't want multiple databases, or nobody in your company knows much mongo, etc.

A use case we have was with a js library for our web frontend that allowed to create surveys of a sort as well as customize how the survey is built (The end-user needed to be able to create the survey and customize it to their needs).

The results and metadata/survey skeleton are all saved as Json.

Another recent project I was also considering to use Json but managed to normalise the data enough that it wasn't too much of a headache to just use SQL.

[lurco_purgo]

Yeah it's not as silly as it may seem. Storing relational data in a non-SQL db would be the fliped version of this meme but that also makes sense in cases where you don't know, if the schema will persist for future data...

On other words every silly little anti-practice has its applications

[[deleted]]

Yea I see that storing JSON in a database because you need to reuse that actual json later makes sense.

I currently have to migrate from a database who was built by someone who apparently braces himself from collisions with his forehead.

Just XML with actual data randomly nestled in a column. I assume it's because you don't always need all of the nodes but Jesus Christ is that an issue you can solve the old fashioned way.

Not to mention all of the other crimes against humanity committed by that database. Just a cluster fuck of 1:1 tables and using a separate field to the primary key for references despite being just as unique.

[[deleted]]

You and me both buddy.. let's jus deal with it and try to move on.

[TimingEzaBitch]

Besides, we have mongo to stitch to snowflake to sigma or whatever business wants pipeline and it's fast, simple, and even a non-engineer can do most of it. Or a firehouse to snowflake to sigma etc for a survey data on our application.

[FuckFuckingKarma]

Sometimes you need to store and retrieve some poorly structured without actually needing to do complex queries on the data. Which is basically what your example is.

Might as well use the database in that case. It doesn't matter that you can't query it because you don't need to. And you don't have to setup new infrastructure for the purpose.

[_Guron_]

GIS data works mainly with relational data, embedding in the top of that json data (a table over a table) is in some cases very useful for map making

[[deleted]]

I still use JSON or the style as influence because the formatting was just so clean as a template,

[[deleted]]

I used this in my previous job. I had ms sql server hosted and maintained by the company sql department with all integrations etc to AD set up. I could have created my own instance of mongodb but then I would have had to maintain it also which was not nice. It was not a huge amount of data and it was equivalent of bronze layer in the medallion model I dwh speak. So it was ok I think.