Best option many to many option and utilize caching to reduce database queries later if you need to.
By:Xtreem Solution
The solution with a table and ones and nulls is not scalable. If you decide to add or remove features, you will need to change the table structure. And even for the storage on the database, it's better than having a table full of nulls.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community