DiscoverNo CompromisesShould we use a JSON field for this?
Should we use a JSON field for this?

Should we use a JSON field for this?

Update: 2024-10-29
Share

Description

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.
Comments 
loading
00:00
00:00
1.0x

0.5x

0.8x

1.0x

1.25x

1.5x

2.0x

3.0x

Sleep Timer

Off

End of Episode

5 Minutes

10 Minutes

15 Minutes

30 Minutes

45 Minutes

60 Minutes

120 Minutes

Should we use a JSON field for this?

Should we use a JSON field for this?

Joel Clermont and Aaron Saray