You don't need NoSQL (use MySQL)
Рет қаралды 74,218
To learn more about PlanetScale, head to planetscale.com/youtube!
MySQL has first party support for JSON documents and it can be a really nice escape hatch from the rigid structure of a relational database.
To learn more, check out some videos from our free course:
* planetscale.com/learn/courses/mysql-for-developers/schema/json
* planetscale.com/learn/courses/mysql-for-developers/indexes/indexing-json-columns
Or some of our blog posts:
* planetscale.com/blog/indexing-json-in-mysql
* planetscale.com/blog/the-mysql-json-data-type
The SQL for the products table shown in the video is available here: www.digitalocean.com/community/tutorials/working-with-json-in-mysql.
---------------
00:00 MySQL supports NoSQL
01:15 When to use JSON
04:20 JSON versus TEXT columns
07:00 Efficient JSON storage
07:45 Creating JSON objects with SQL
11:00 Extracting JSON from the document
14:40 JSON arrays
17:20 Querying on JSON columns
18:50 Query an array's items
19:40 Indexing JSON documents
22:48 Generated columns
26:00 JSON blob storage
27:09 Making JSON invisible
29:00 Updating documents in place
---------------
💬 Follow PlanetScale on social media
• Twitter: planetscale
• Discord: discord.gg/pDUGAAFEJx
• TikTok: www.tiktok.com/@planetscale
• Twitch: www.twitch.tv/planetscale
• LinkedIn: www.linkedin.com/company/planetscale
@rdvansloten 9 ай бұрын
This channel pumps out quality database content every week. Definitely deserves more subscribers.
@PlanetScale 9 ай бұрын
😮💨 I appreciate that
@aWebExpert 8 ай бұрын
Done!
@Zomp420 8 ай бұрын
good point! I just subscribed
@davidmutua6971 6 ай бұрын
Done. Was really a noob mysql Developer hidding behind Eloquent. Now I can review some senior dev codebases. Thanks Franco.
@LenWoodward 9 ай бұрын
I'm absolutely loving this long-form content, Aaron. So easy to just put each one of these in my `favorites` list. So much value.
@PlanetScale 9 ай бұрын
Thank you Len! They're a lot of work so I'm glad to hear that
@xcrap 9 ай бұрын
I have never used, and probably will not, but I have to admit, that's incredibly powerful. Super educational information as usual. I think the only thing missing in some videos would be some real-case measurements and testing. For example, there could be two tables: one with JSON elements and another without. We could compare the speed of SELECTs from a million table data. I think this will not only be useful but also very informative about what kind of tables or schemas are more suitable for specific case scenarios. For example It could help us make informed decisions when creating product items attributes in a shop, whether it's better to use JSON or just columns. MYSQL is really powerful ;)
@antonmykhailovskyi447 8 ай бұрын
I don`t really often leave comments but you deserved it)) Ngl, I`ve never seen neither more useful, nor "pleasant-to-listen" tutorials in MySQL topic. The way you, Aaron, explain things to us is out of this world, do love it! Keep it up, I`m completely sure many people will find it useful!
@PlanetScale 8 ай бұрын
What a great start to my week, thank you so much!
@0xjrr 9 ай бұрын
This series of videos are incredible, been watching all of them and it really helps me out. Thanks for your work, keep it going.
@PlanetScale 9 ай бұрын
Thank you! Nice to know it's helping people
@MatthiasFeist-de 9 ай бұрын
those videos you make are really great. I worked with mySQL since 15 years ago but I still learn something new and really enjoy the format and your delivery of these topics!
@PlanetScale 9 ай бұрын
Means the world to me, thank you
@nathanbrown2640 9 ай бұрын
Three minutes into watching this, and I'm already loving the wonderful variety of use cases you have come up with! Feels like a NoSQL approach within a relational db
@PlanetScale 9 ай бұрын
Thanks! Kinda crazy right?
@mkmalikcom 9 ай бұрын
@@PlanetScaleright
@MrOptima 8 ай бұрын
Excellent video and resource link to Digital Ocean. I was living in dark ages using MySQL version 5.2x. I upgraded to 8.0.35 and experimented with everything you mentioned in the video. It opened my eyes on how to use MySQL with JSON moving forward. I was using a text field for that before and did not know about all the JSON related functions of MySQL. Thank you very much.
@Cookie-mv2hg 8 ай бұрын
I love your courses and the way you explain about things. Please keep doing it!
@kyleareich 7 ай бұрын
Dude you're one of the best teachers I've ever run across on the internet or in person. Thanks for what you do. I love your videos.
@PlanetScale 7 ай бұрын
This is one of the nicest things I've ever heard. Thank you internet stranger, I really really appreciate it
@kilian7919 8 ай бұрын
I really enjoyed this tutorial. I'm new to DBs as a whole, getting this insight into how JSON-Documents can be handled independently of a NoSQL-DB will surely be useful. I will hopefully be doing a project for changelog-storage in the near future, where this might come in handy!
@Tigerlady22445 8 ай бұрын
I just stumbled across this video and I haven't finished it but I already love it! I'm still learning about databases but I thought NoSQL was hands down more powerful and scalable than SQL tables, and my previous experience with SQL tables has been a drag, but this is showing me a side of SQL tables I didn't know existed. Thanks!
@BudaSuyasa 8 ай бұрын
Wow, i been using MySQL all of my career and this video blown my mind. So much value as always Aaron.
@rasalas91 9 ай бұрын
I saw the field type a few months ago and it blew my mind. It felt like everything NoSQL was "known good for" just "vanished". I can just keep using MySQL for most of my stuff :D I still didn't know about some of the things you showed, so thanks
@ANIALLATOR114 9 ай бұрын
Awesome video content as always! Love seeing a video from this channel pop up in my feed ❤
@cedantarmalabori861 7 ай бұрын
Unreal the quality of content you are putting out. I've made the decision to not use NoSQL db's for certain services thanks in part to this video. Keep it up. Super informative.
@ahmad-murery 9 ай бұрын
I know all of the mentioned JSON function but I really didn't know about array range path and the member of operator, I used json column in many cases but the most useful one was in this scenario: I have 2 tables, one for user notifications and the other for email queuing, each notification/email has a specific template and parameters according to its type and language, the problem is that a user can change his display language any time and he should still be able to read his notifications and emails (that are not sent yet) in the selected language, as you can see here it's not possible to store the notification/email in its final shape, or store it in every possible language, so I stored all the params needed to render the notification/email in a json column and then merge them with the template at runtime. Thanks Aaron! it was a great video as expected 👍
@PlanetScale 8 ай бұрын
That's really clever. I like that example, thanks for sharing!
@kirayamato6128 9 ай бұрын
I really liked your tutorials and content. It feels like I learned new functionalities every single video. Keep it up dude!
@PlanetScale 9 ай бұрын
Thank you!
@roschereric 8 ай бұрын
Awesome first contact with your channel :) thank you for the quality content!
@PlanetScale 8 ай бұрын
🫡 glad you enjoyed it!
@arielspalter7425 8 ай бұрын
Excellent tutorial. Eloquently and clearly explained and demonstrated.
8 ай бұрын
I did exactly that in a postgresql db. This is fantastic, much more solid and fast
@Boubiboom 9 ай бұрын
This is so good, you do an amazing job !! It’s crystal clear, we learn a lot, thank you very much ! 👍
@asathler 8 ай бұрын
Awesome features at MySql. Thanks for this impressive lesson! Regards from Brazil.
@ukaszzbrozek6470 8 ай бұрын
This video widened my understanding what can be done with MySQL. Thank you !
@carnavalesenpanama 8 ай бұрын
I love this channel so much. Aaron, you are the best
@PlanetScale 8 ай бұрын
🫶 that means the world to me
@AdrianBav 8 ай бұрын
Great video, thanks! A few months back I watched your full MySQL course and have drafted an improved version for part of our app utilizing a JSON column. We have 3 (currently) types of specification/schema from APIs which we need to store for reference before normalizing. Currently they have all been saved in the same table with column name variations and lots of NULL values for N/A columns, etc 😢 One improvement would be to use separate tables for each type. Another would be to store each raw specification in a JSON object which is what I've experimented with. I've used a dynamic cast on the eloquent model to hydrate the data into the appropriate DTO when fetched. I've also made the JSON column invisible :) Some common high level stats are in the non JSON columns, and the raw data is there if needed. Seems like a tidy solution for our needs.
@ernestmugo1765 8 ай бұрын
Managed to get me glued to the screen for more than 30 minutes. Cool video
@PlanetScale 8 ай бұрын
Yesss that's a feat! Glad you liked it
@Sabach9397 9 ай бұрын
We often have an "options_json" column where we set configurations of things that we don't directly search often. An example would be on our forms builder, the forms settings someone picks we use to generate the form, or even on questions if a certain question type is required or has visibility requirements, etc. It saves scanning a ton of extra columns.
@philliptune 8 ай бұрын
Right, I had kinda assumed that, while you could, you wouldn't really want to search using JSON data columns. I've just been using it for mostly what he mentioned, metadata, settings, and I like the idea of tenant-specific data structures as I'm currently working in a multi tenant app that we're building out integrations for.
@philliptune 8 ай бұрын
I didn't expect to watch this whole video. You got me excited about JSON. I've already been using it for some metadata columns, stored as TEXT, for a PHP Laravel project . And as we want to use only Db-agnostic query operations, we've shied away from JSON-specific operations that might not be implemented in any major Db drivers we're using. But after watching this I'm going to dig more into the latest Eloquent query builder helper functions as well as possible common raw syntax that might be shared between our supported RDBMs.
@PlanetScale 8 ай бұрын
Yessss I'm so glad to hear that you stuck around! You've correctly pointed to a good caveat with JSON, it's not exact across all vendors. But! Might as well use the full power of the DB you've chosen, versus sticking to the lowest common denominator. Excited to hear what you get up to!
@vcbiotech 9 ай бұрын
I had fun. This was amazing. THANK YOU. Trying to manage so many EAVs was killing me, and the idea behind that was having a future analytics integration. This is much easier.
@PlanetScale 8 ай бұрын
Glad to hear it!
@joanvanduren2239 9 ай бұрын
a clear and practical story, told by a passionate and skillfull db teacher
@noabald 8 ай бұрын
I almost never touch databases as a frontend, but the videos you make are super interesting. I’m glad you’re giving me a glimpse into my backend friend’s world and hopefully I can help work with them better
@PlanetScale 8 ай бұрын
Love to hear that! Thanks for telling me
@daknyx1448 8 ай бұрын
Currently using a relational DB for a private project after a while of using exclusively MongoDB in the professional context, and this video has a perfect timing to solve one of the issues I had: having a list of (unknown amount of) tags for any row. Currently I am using extra link tables but a json column would do the job in a more elegant manner imo. Thank you!
@PlanetScale 8 ай бұрын
Tags are a great use case for sure. Glad it was helpful!
@jslime 7 ай бұрын
Incredibly useful tutorial. Thank you for putting it together.
@jslime 7 ай бұрын
After playing around with this today. Some useful notes for MariaDB users: 1.) The ->> operator is a shorthand for JSON_UNQUOTE(JSON_EXTRACT()) in MySQL 5.7.13 and later. However, MariaDB does not support this shorthand operator. You're stuck with JSON_UNQUOTE(JSON_EXTRACT(`jsonObject`, '$.your_key')). 2.) When attempting to create STORED or VIRTUAL columns; instead of STORED use PERSISTENT: eg: ALTER TABLE your_table ADD COLUMN your_column VARCHAR(255) AS (JSON_UNQUOTE(JSON_EXTRACT(`jsonObject`, '$.your_key'))) PERSISTENT; 3.) The INVISIBLE column feature is not supported in MariaDB. It's a feature introduced in MySQL 8.0.23, which allows you to make a column invisible. In MariaDB, you can't make a column invisible directly.
@pulanski 9 ай бұрын
excellent vid man. keep em coming. great stuff
@havvg 9 ай бұрын
Great content, Aaron. I have been using the JSON type for quite a long time, but wasn't aware on the index part of that topic (and never was in need of it, yet). Aside from the typical log scenario (API Tx/Rx), I have been using JSON for event stream data, basically the same, but from an event sourcing view on the domain.
@PlanetScale 8 ай бұрын
Mmm I like that. Event stream is a great example.
@hassamulhaq7762 8 ай бұрын
really thanks for covering this JSON topic.
@gebi84 9 ай бұрын
Mindblowing 😮, doesen't know any of this JSON functions. Thank you for sharing!
@timucinbahsi445 8 ай бұрын
I'd like to add to this. Some of the reasons for using NoSql are being able to store the data in RAM like using Redis for cache etc and also NoSql is scalable. Both of those also possible in Sql databases. You can definitely configure your db to be stored in the memory and you can definitely have a cluster of Sql database. It is harder to scale up relationships with both Sql and NoSql. NoSql just defaults to having no relationships what so ever. That's what makes it easier to scale. If you do introduce relationships in your data, you'll have the same issues. Needless to say Sql databases are perfectly capable of not using relationships
@JacquesvanWyk 8 ай бұрын
Wow this is great content. I have to do some database queries at work and loving these tips and tricks.
@PlanetScale 8 ай бұрын
Thank you!
@simonnjoroge933 8 ай бұрын
Once again, I am in love with databases and planning to be the SQL Chad. Database with this guy, amazing. Great Content, do MORE. 🌟😃
@PlanetScale 8 ай бұрын
🫡🫡 more on the way
@pertsevds 9 ай бұрын
I just love your videos explaining MySQL ♥
@PlanetScale 8 ай бұрын
🫶 thank you!
@bensonnjonjo 9 ай бұрын
complex topic very well broken down, thank you
@arcanernz 9 ай бұрын
Didn't know you could create an index on a json array, very useful, and making those blobs invisible is a good tip.
@orathaic 8 ай бұрын
I had my space ship game allow (no require) players to design their own spaceships, and I stored the designs as a json blob. But I that was before I knew it could be a json column rather than a text blob. So this is awesome!
@PlanetScale 8 ай бұрын
Nice! Glad it helped
@BradleyBernard 8 ай бұрын
Amazing video once again! I knew JSON support existed but didn’t know to that depth 😮 Topic suggestion: would love to see a deep dive 30m video on foreign keys: performance, alternatives, when to use vs when too much (ie a massive join table with FKs can be slow inserts), db support (and why?!), cascade behaviors as related to app logic (why null on delete can be bad for app logic), etc. maybe this is covered in your MySQL for devs vid, but can’t remember Also I find these videos to be a gold mine - any thoughts on doing a (cliche but useful) chat bot or similar product to be able to natural language query your video content? I don’t have a use case today for JSON, but might want to search PlanetScale or Aaron’s video catalog to see snippets from all indexed videos and jump to specific pieces to re-watch… not sure if others are asking too but might be worth a
@PlanetScale 8 ай бұрын
Yeah this is a great great great idea. I need to beef up our content on foreign keys. Added to my list! Also suuuuper interesting idea about a chatbot! Could totally do it, I think
@PublyoRaymundo 8 ай бұрын
Nice video. Would be good to see some performance numbers on the queries, specially when using them on predicates
@adam-xt8te 8 ай бұрын
Friendly and kind developer you are, sir
@GulzarAhmed7 8 ай бұрын
Mazedaar video banate ho Aaron bhai
@Imjoshnewton 9 ай бұрын
Love this content! My use case for the JSON column type is storing additional data on a task table. We have an automation pice in our platform with workflows that contain stages that contain tasks. Each task type can have different data associated with it. Saves me from having a bunch of nullable columns or cluttering up the database with extra tables for task data. I use Zod to validate the inputs as they go into the table so I get the flexibility of JSON and some schema validation.
@PlanetScale 8 ай бұрын
Ooo nice thinking to use Zod on top of it.
@LokmanMusliu 8 ай бұрын
@@PlanetScale for the Laravel folk, you can do the same by casting your JSON column to a DTO. You will have schema and type validation.
@SSeeiicckk 9 ай бұрын
In my case I used the JSON column to make sure to get steps that must be followed. This could be changed from task to task, so I realized I could use it instead of just having another NoSQL DB running and waisting resources for this purpose when I can use the same MySQL DB. Of course, this depends on its use and how many times this table will be read and/or written. If iit comes to be a bottleneck for my case I would change it to a single microservice for this purpose but this is far beyond the usage now. Amazing content! Thank you!
@PlanetScale 8 ай бұрын
Nice, that's a great use case! Thank you for sharing.
@GergelyCsermely 8 ай бұрын
Thanks. Excellent tutorial.
@RajveerSingh-vf7pr 8 ай бұрын
Today(after weeks) I realized that this is an official channel... I have never seen such a great quality content from an official channel...
@PlanetScale 8 ай бұрын
🥰 love to hear that.
@juzmamfull 9 ай бұрын
Radzio jest fajny! Dzięki za video!
@zee-ut9vz 8 ай бұрын
Thumbs up for pointing out the nuances, learning this the hard way as senior engineer could be painful...
@cybermanne 5 ай бұрын
Really good stuff here!
@kaisarcode2 7 ай бұрын
OMG, this is mind blowing!!! ❤❤❤
@OnAirMarc 9 ай бұрын
I have so many ideas on how I'm going to use this for supporting custom user defined fields in a CRM I'm building! Thank you!!!
@PlanetScale 9 ай бұрын
Niiiice! Do report back!
@lighty262 9 ай бұрын
I would love to hear more about subqueries next time, when to use it and when not to use it, as well as the drawbacks.
@PlanetScale 8 ай бұрын
Nice, I'll do a whole video on that
@peterl.8681 8 ай бұрын
It's pretty nice to have json in sql. Although still figuring out how to do a where in on a json array.
@ESArnau 8 ай бұрын
This guy is a good dev rel, kudos
@delamberty 9 ай бұрын
This is absolutely gold.
@PlanetScale 8 ай бұрын
🫡 thank you!
@stephenpaek9175 6 ай бұрын
Excellent, thank you
@iliesboukhatem7803 9 ай бұрын
great video ! thank you so much
@rid9 8 ай бұрын
Another idea for JSON data: audit history. For example, don't just have a created_at and updated_at for a user, but also history which contains a log of when the update happened, what changed and who initiated the change.
@PlanetScale 8 ай бұрын
Audit history is a good one! I actually use JSON for that exact use case in an app I built.
@user-qf5be9km6o 9 ай бұрын
why am I enjoying this content so much lol
@PlanetScale 9 ай бұрын
🙈 I dunno but please keep watching
@dynamohack 9 ай бұрын
You are the only guy who derailed the nosql train with already battle tested mature technologies ❤❤❤❤❤
@blender_wiki 8 ай бұрын
Json in a MySQL field makes so much sense that I have a hard time imagining people that don't see this as an advantage. Unless you need to store BIG data managing a Json in a MySQL solves so many problems in development and is very flexible if in the future you want to move your Json to a noSQL instead of adding undress of tables and filed and get mad with conversation.
@MaltheMinecraft 9 ай бұрын
Your videos are great
@SaiyanJin85 8 ай бұрын
I'm soooo gonna use it. I'm not sure about performance wise, for example, you have 100.000 product rows and you want to query their options or another case what about joins between a json attribute with another table. A use case for that: - again a product row with json column for its options but you don't want to store the actual name of let's say the color but it's id because if you change color value you have to update all the products that contain this color
@BatmanBruceWayne 9 ай бұрын
I assume that you, as every person on the planet, would like to retire someday. Against that idea, I'd like to ask you never to stop making videos. I love all of them!
@PlanetScale 9 ай бұрын
It's not happening any time soon 🫶🫡
@uncopino 8 ай бұрын
sometimes even if a schema is well defined, putting some properties (like additional data with low redundancy and that isn’t used in queries) in a json blob is a good alternative to enormous tables or one to one relationships.
@petruciucur 8 ай бұрын
Brilliant !!!
@knightofrohan 9 ай бұрын
Interesting! I am just learning dev and my first foray into it is with WordPress. I know WordPress plugins like Elementor use JSON for the pages you build in them and I wonder if they use this feature of MySQL.
@viniciusataidedealbuquerqu2837 8 ай бұрын
thank you editor
@zille3000 8 ай бұрын
The dollar sign and the array handling are actually part of JSONPath and can be used in jq and other fun tools. I would expect having full JSONPath syntax there.
@PlanetScale 8 ай бұрын
Oh neat! I didn't know that. Thanks for sharing
@jimg8296 7 ай бұрын
Wow .... Head Wall! Link to your videos to team tomorrow.
@yatskanych_oleksandr 8 ай бұрын
Thank you a lot!
@PlanetScale 8 ай бұрын
🫡🫡
@joshuastories 9 ай бұрын
Thank you
@avishjha4030 8 ай бұрын
Wow, never knew this was possible!
@jatazoulja 8 ай бұрын
been using jsonb for 5 years now, good thing like on postgres, I can index json keys.
@lacherolachero9409 8 ай бұрын
Great content! Love it! Btw, what is this tool you are using to interact with the db?
@developerpranav 8 ай бұрын
Damn MySQL is nice! Didn't know about these neat tricks it has for json. I'll use these when working with json in my projects, and definitely no need for NoSQL! Thanks!
@PlanetScale 8 ай бұрын
🫡🫡
@JoseRodriguez-rx4ck 8 ай бұрын
This info is super useful, at work we are evaluating ditching MySQL for PostgreSQL and get a NoSQL. I know nothing about NoSQL, is it possible to do a second part of this video explaining how these MySQL features compare to NoSQL?
@joinparky 3 ай бұрын
Very Very good 👍
@Kane0123 9 ай бұрын
All you need is one table with one row with one cell to store an entire nosql database. Winning!
@PlanetScale 9 ай бұрын
Mega brain idea
@duramirez 8 ай бұрын
I think Logging is one good use case for Json blobs, because logs often have specific data related to where this log is coming from, and it's always a pain to work with it in relational dbs. 🤔 Ofc, its mostly for storage, not for constant query. :)
@mme725 9 ай бұрын
Holy crap, that 'set invisible' bit blew my mind 🤯
@PlanetScale 9 ай бұрын
Feels like that could be a standalone video huh! Wild right
@clamhammer2463 8 ай бұрын
Is there a way to set up a mysql database to natively push updates to tables/rows much like some cloud providers offer?
@neverything 8 ай бұрын
Used it for API responses where I might need additional values later on
@OM-bs7of 8 ай бұрын
What about wide column store like Scylla DB? I think hy no SQL he is referring to mongodb. The problem with relational dbs is scaling horizontally
@wcrb15 8 ай бұрын
I work with a platform that utilizes the EAV pattern A LOT. It would be so nice to do that json grouping sometimes instead of the millions of joins required to get everything back 😂
@bertilow 9 ай бұрын
Gold content
@bmeares 9 ай бұрын
Incredible, I wonder how this compares to PG's JSONB🤔
@PlanetScale 9 ай бұрын
Same actually. What are you most curious about: functionality or performance?
@kirayamato6128 9 ай бұрын
I think when it comes to databases like queries, performance really matters
@yarmgl1613 8 ай бұрын
@@PlanetScale performance benchmarks video would be nice
@123mrfarid 8 ай бұрын
@@PlanetScaleperformance comparison with json postgres please, also with jsonb
@inwerpsel 8 ай бұрын
14:57 Wow, it even supports the SQL pattern where it's fundamentally undecidable whether you should use singular or plural names.
@PlanetScale 8 ай бұрын
Some things never change
@user-yv2cy9pq1y 8 ай бұрын
You have been doing really good effort for everyone, it's really nice. I was wondering if you need a video editor team of motionscope, to take your channel to new heights with professional editing.
@PlanetScale 8 ай бұрын
We have a Steve the Editor. Thanks tho!
@thedelanyo 9 ай бұрын
The array accessing by index range is kinda crazy, it's like slicing 😊😊
@simonegiuliani4913 8 ай бұрын
Majority of people use nosql for horizontal scalability
@MikeKasprzak 9 ай бұрын
That was epic. 🤯 I'm running an old MariaDB version that "probably" didn't support this, so I created my own metadata table with its own funny rules to get JSON-like outputs. Most of my metadata is just extra data, but some represent relationships between nodes. That was not always the case though (relational metadata used to be a separate table). For the most part I haven't needed to index the non-relational metadata, but seeing that indexing actually works anyway has me scratching my chin. 🤔 Also that array multi-value index thing is just bonkers 🤯. I'm trying to decide if this could work to simplify how I handle multiple tags and multiple authors. 🤔
@PlanetScale 8 ай бұрын
So much fun stuff right?! I don't know how much MariaDB supports, but it's definitely worth looking into
@2chiem369 8 ай бұрын
Can you make a video about using json in mssql
xunyu
Рет қаралды 1,5 МЛН
Павел Хмурчик
Рет қаралды 323 М.
LED Screen Factory-EagerLED
Рет қаралды 6 МЛН