{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"No Compromises","title":"Should we use a JSON field for this?","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/8b618a8f\"></iframe>","width":"100%","height":180,"duration":860,"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.Want a place to ask any question related to Laravel development? Check out the Mastering Laravel community.","thumbnail_url":"https://img.transistorcdn.com/Z2EtRaIjEnyUZU7bc944H_cjygcmUk4l_35aeIjws5o/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzIzMDM3LzE2Mjc1/MjExMTAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}