Sign up to save your podcasts
Or
Share Should we use a JSON field for this?
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Should we use a JSON field for this?
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
Want a place to ask any question related to Laravel development? Check out the Mastering Laravel community.
View all episodes
By Joel Clermont and Aaron Saray
4.9
88 ratings
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
Want a place to ask any question related to Laravel development? Check out the Mastering Laravel community.
More shows like No Compromises
View all
The Laravel Podcast
57 Listeners
Startups For the Rest of Us
697 Listeners
Connected
568 Listeners
Laravel News Podcast
56 Listeners
The Laracasts Snippet
76 Listeners
North Meets South Web Podcast
24 Listeners
Syntax - Tasty Web Development Treats
987 Listeners
No Plans to Merge
50 Listeners
Notes On Work - by Caleb Porzio
17 Listeners
The Rest Is History
14,371 Listeners
Mostly Technical
27 Listeners
Talking Businessly
2 Listeners
The Business of Laravel
7 Listeners
Slightly Caffeinated
0 Listeners
The Panel
4 Listeners