Laravel: Separate DB Tables for Roles? I Don't Recommend It
This is my opinion on the way of structuring DB profiles for users like "admins" and "users" in separate tables.
Full lesson: "Booking.com API: Profile Fields Structure" https://laraveldaily.com/lesson/booki...
- - - -
Support the channel by checking out my products:
My Laravel courses: https://laraveldaily.com/courses
Laravel QuickAdminPanel: https://quickadminpanel.com
Livewire Kit Components: https://livewirekit.com
- - - -
Other places to follow:
My weekly Laravel newsletter: https://us11.campaign-archive.com/hom...
My personal Twitter: / povilaskorop
![[09/10] Laravel Travel API: Laravel Pint and Larastan](https://images.videosashka.com/watch/iVhOVxEyjFE)
![[07/10] Laravel Travel API: Admin Endpoint to Create Tour](https://images.videosashka.com/watch/glDKQxYSJlw)
![[03/10] Laravel Travel API: Public Endpoint for Tours with Tests](https://images.videosashka.com/watch/YU-26bqHP7U)
![[02/10] Laravel Travel API: Public Endpoint with Pagination and Tests](https://images.videosashka.com/watch/fJYJMFr6FuE)
![[01/10] Laravel Travel API: DB Schema - Models and Migrations](https://images.videosashka.com/watch/9aIVmiL3Xks)
