Share
Thanks for visiting The Cell Phone Junkie! I will be taking the time each week to discuss my favorite topic, cell phones. Any feedback is appreciated and welcome. You can email me at: questions (AT) thecellphonejunkie (DOT) com or call: 206-203-3734 Thanks and welcome!
…
continue reading
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://staging.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?
140 episodes
))
