JSON is the data interchange format of choice. But its performance in a relational database is horrible. RDMS are built around standard data types such as INTERGERS and CHAR. There are many good reasons to store data in JSON in your database, but you give up many powerful features of SQL to do so. The answer is JSON_DATA(), which *temporarily* converts JSON to relational data types, unleashing Window Functions, Aggregates, and more. You will learn how to perform simple conversions with JSON_TABLE(), move on to working with embedded data, and handle missing data or errors. Finally, we will look at alternatives that can be faster, such as materializing the data or using other JSON functions.

Comments

Please login to leave a comment

Anna Filina at 10:14 on 16 Oct 2026

Interesting topic. Well presented: good pace, information-dense, straight to the point, simple and clear examples. Thank you! Font a bit small on some slides.

Very interesting talk that I was immediately able to apply to my work app's database to try out, which is always a bonus. We don't use Postgres but demonstrating both side-by-side was appreciated. I don't like Postgres syntax, it seems extra complicated. I also appreciated the tradeoffs of using tables vs. not, it helps curb the "let's deploy this thing now!" temptation.

Mark Priddy at 17:08 on 16 Oct 2026

Thank you for the introduction