Level 1
Jul 15, 2022
7
Level 9
DB Schema
Hello guys, I am building an app with Laravel, and get a bit confused about the DB schema to use. Here is my scenario: The app has different types of clients: Accounts, wholesalers, and Internal Reps. Each type will have several users that will need to login and submit orders. My first thought was to have 3 tables a users table for the internal reps, accounts_users, and wholesaler_users tables for the rest. I need your advice guys and please can you share any best practices for this use case? Thanks
Level 73
Stick with one users table, there is no difference between them when it comes to authentication, it's when you need to authorize the different users that the work should be done. You can do that with roles.
Spatie has a nice package for that.
2 likes
Level 9
Hello guys, Thank you so much for your returns. What do you think of the single table inheritance approach?
Level 122
if you need to store different attributes, you could try the polymorphic approach
http://novate.co.uk/using-laravel-polymorphic-relationships-for-different-user-profiles/
and i would definitely avoid using different guards
2 likes
Level 9
@Snapey Thank you. I think the polymorphic approach is more adapted for my use case.
I will set up the User Model to be shared by other models. That way I can add permissions and roles to control actions.
Thank you guys for all your responses 👍👍
Please or to participate in this conversation.