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://staging.podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Should we use a JSON field for this?

14:20
 
Share
 

Manage episode 447362524 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.

JSON fields can be very useful, but when is a good time to include them in your database design?

In today's episode of No Compromises, Aaron and Joel use a couple examples from recent projects to talk through reasons they would and would not use a JSON field.

  • (00:00) - Debating JSON fields in database design
  • (03:06) - Configuration options: JSON vs. relational tables
  • (07:05) - Real-world example: label customization dilemma
  • (11:30) - Silly bit

Want a place to ask any question related to Laravel development? Check out the Mastering Laravel community.
  continue reading

125 episodes

Artwork

Should we use a JSON field for this?

No Compromises

18 subscribers

published

iconShare
 
Manage episode 447362524 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.

JSON fields can be very useful, but when is a good time to include them in your database design?

In today's episode of No Compromises, Aaron and Joel use a couple examples from recent projects to talk through reasons they would and would not use a JSON field.

  • (00:00) - Debating JSON fields in database design
  • (03:06) - Configuration options: JSON vs. relational tables
  • (07:05) - Real-world example: label customization dilemma
  • (11:30) - Silly bit

Want a place to ask any question related to Laravel development? Check out the Mastering Laravel community.
  continue reading

125 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.

 

Listen to this show while you explore
Play