How Well Do Relational Database Engines Support JSON?
summary
Comparative survey of MySQL, PostgreSQL, Oracle and SQL Server evaluates actual JSON features against SQL:2016 defines 22 JSON features, finds Oracle closest to full support, and shows real differences: PostgreSQL offers both json and jsonb (binary format with indexes and different duplicate‑key behavior), MySQL has a JSON type but limited standard conformance, and SQL Server exposes JSON via FOR JSON / OPENJSON. The standard lacks a JSON modification primitive, implementations vary on validation, indexing and query functions, and Postgres 12 promises fuller SQL/JSON path support.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:01Agenda
- 1:28Multimodal Databases
- 3:23JSON Use Cases
- 7:03JSON Standard
- 11:53JSON constructors
- 13:37JSON objects
- 16:42Functions
- 20:20Storing JSON
- 22:35Storing Integers
- 26:56MySQL and Postgres
- 32:50Implementation
- 34:18Operators
- 37:31Database Implementation
- 39:59Indexing
- 40:55Structure
- 41:40Summary
related talks
48mHow Well Do Relational Database Engines Support JSON?
47mDealing with JSON in the Relational World
51mDealing with JSON in the relational world
48mThe road to new SQL/JSON features
01h 06mSQL ❤️ JSON: The Best of Both Worlds
30mJSON support in MySQL
49mShould I use JSON in PostgreSQL?
05mPostgreSQL JSON JSONB Making the Right Choice for Your Application