1

I am used to MSSQL, now using MySQL, and have come to a point, where it is convenient to dump a whole JSON object into a single db column, instead of hacking it away into separate ones, in a relational database fashion. Most of the time, I will just SELECT the whole object back into the app when needed, but occasionally, I will want to filter rows according to contents of the JSONs and maybe do some other operations.

Is working with JSON objects "native" to MySQL, or is it kinda hammered it, for extended usability (JSON_EXTRACT, JSON_MERGE..), while sacrificing performance, and therefore not a good way to go?

1 Answer 1

1

Its native to MySQL and works very smooth.

Read through this example.. its pretty simple and useful

https://scotch.io/tutorials/working-with-json-in-mysql

Sign up to request clarification or add additional context in comments.

2 Comments

I actually wrote this question while going through that tutorial :) Any stats on how it performs compared to standard non-JSON CRUD?
I don't see any difference with millions of rows on 2 level JSON objects. I love the combination of RDBMS with JSON flexibility though.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.