Support the ongoing development of Laravel.io →
murilolivorato
posted 7 years ago
Eloquent Testing
Last updated 2 years ago.
0
xtreem-solution
replied 7 years ago

Best option many to many option and utilize caching to reduce database queries later if you need to.

By:Xtreem Solution

Highly Skilled Laravel Developer

Dedicated PHP Developer

0
caiquecastro
replied 6 years ago

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.

0

Sign in to participate in this thread!

Eventy

Your banner here too?

murilolivorato murilolivorato Joined 24 Oct 2016

Moderators

We'd like to thank these amazing companies for supporting us

Eventy
Fathom
Forge
Envoyer
Beyond Code
BairesDev
N-iX

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

Laravel.io

Forum Articles Pastebin

Socials

X (Twitter) Bluesky Bluesky GitHub

The community

Laravel Laravel Laravel News Laravel News
Laracasts Laracasts Laravel Podcast Laravel Podcast
© 2024 Laravel.io - All rights reserved.
Terms of service Privacy policy Advertise