Season 2 · Episode 1938
Why JSON's "Number" Type Breaks SQL Databases
Mapping JSON to SQL isn't as simple as it looks. Discover the hidden traps in data types that can cause performance hits and data corruption.
My Weird Prompts · Daniel Rosehill
April 3, 202630m 4s
Audio is streamed directly from the publisher (dts.podtrac.com) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
That JSON object in your API has to live somewhere, and that home is usually a SQL database. But translating between JSON Schema and SQL types is a minefield of subtle traps. This episode dives into the "impedance mismatch" between these two worlds, revealing how a simple type choice can lead to performance degradation and data integrity nightmares. We explore the dangers of JSON's vague "number" type, the modern-day Y2K problem of 32-bit integers, and why you should think twice before storing a UUID as a simple string.