Level 52
In your case you have a simple polymorphic relation between users and other tables. You need morphTo in users (with 2 fields like userable_id and userable_type to get id and type from the other table) and morphMany in the others.
Nov 24, 2014
4
Level 2
is this polymorphic relationship or DB design issue ?
There are separate models for students, lecturers, coordinators and all of them are users. I can't figure out the relationship.
Level 6
first path : you can relate all the Entities to user as polymorphic relation .
second path to use multi auth package which will allow you to use any of this Entities as User with Laravel authentication system .
Level 3
Check out this blog post by Richard Bagshaw he sums a good approach pretty neatly. Going to be implementing this in a project I'm just starting and it sounds like it fits the bills for you too
http://richardbagshaw.co.uk/blog/laravel-user-types-and-polymorphic-relationships/
1 like
Level 52
I thought you had a 1:n relation between your tables, but actually it's a 1:1, so you need morphOne.
Please or to participate in this conversation.