Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Discussing different ways to model data

11:50
 
Share
 

Manage episode 520574537 series 2974897
Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

It's easy to overcomplicate data modeling, especially when enums, relationships, and future requirements are in play.
In the latest episode of the No Compromises podcast, Joel brings Aaron a real-world technical dilemma: how to model a relationship between two models when types are stored as enums, not models.
We discuss the pros and cons of pivot tables versus JSON columns, the importance of context before jumping to solutions, and how developer instincts can sometimes get in the way of clarity.

  • (00:00) - Setting up the technical problem
  • (02:00) - Pivot tables vs JSON columns
  • (05:15) - Filtering and validation considerations
  • (07:15) - Deciding on the best approach
  • (09:50) - Silly bit

Would you like us to review your code or application architecture?
  continue reading

140 episodes

Artwork
iconShare
 
Manage episode 520574537 series 2974897
Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

It's easy to overcomplicate data modeling, especially when enums, relationships, and future requirements are in play.
In the latest episode of the No Compromises podcast, Joel brings Aaron a real-world technical dilemma: how to model a relationship between two models when types are stored as enums, not models.
We discuss the pros and cons of pivot tables versus JSON columns, the importance of context before jumping to solutions, and how developer instincts can sometimes get in the way of clarity.

  • (00:00) - Setting up the technical problem
  • (02:00) - Pivot tables vs JSON columns
  • (05:15) - Filtering and validation considerations
  • (07:15) - Deciding on the best approach
  • (09:50) - Silly bit

Would you like us to review your code or application architecture?
  continue reading

140 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play