FK Reference multiple tables. Database relations and foreign key constraints in Laravel
I have a "Files" table (id, Name, Path, Owner). I want to link the Owner column to multiple tables (students, supervisors ...). For example the owner of a file could be a student, supervisor or Evaluating committee. What is the efficient solution to this problem since I can not reference a foreign key to multiple tables?
php mysql laravel
edited Nov 21 '18 at 9:11
Armali
7,020936100
asked Nov 20 '18 at 20:16
Souleiman FadalSouleiman Fadal
62
add a comment |
I have a "Files" table (id, Name, Path, Owner). I want to link the Owner column to multiple tables (students, supervisors ...). For example the owner of a file could be a student, supervisor or Evaluating committee. What is the efficient solution to this problem since I can not reference a foreign key to multiple tables?
php mysql laravel
edited Nov 21 '18 at 9:11
Armali
7,020936100
asked Nov 20 '18 at 20:16
Souleiman FadalSouleiman Fadal
62
1
You could have separate connecting tables for each possible owner, or restructure you database so that student, supervisor, and committee tables are all in one "users" table (and differentiated by a user type field); with optional student_details, staff_details, and/or committee_details tables for information unique to the different types.
– Uueerdo
Nov 20 '18 at 20:20
This might be a good start: stackoverflow.com/questions/7844460/…
– adam
Nov 20 '18 at 21:41
add a comment |
I have a "Files" table (id, Name, Path, Owner). I want to link the Owner column to multiple tables (students, supervisors ...). For example the owner of a file could be a student, supervisor or Evaluating committee. What is the efficient solution to this problem since I can not reference a foreign key to multiple tables?
php mysql laravel
edited Nov 21 '18 at 9:11
Armali
7,020936100
asked Nov 20 '18 at 20:16
Souleiman FadalSouleiman Fadal
62
I have a "Files" table (id, Name, Path, Owner). I want to link the Owner column to multiple tables (students, supervisors ...). For example the owner of a file could be a student, supervisor or Evaluating committee. What is the efficient solution to this problem since I can not reference a foreign key to multiple tables?
php mysql laravel
php mysql laravel
edited Nov 21 '18 at 9:11
Armali
7,020936100
asked Nov 20 '18 at 20:16
Souleiman FadalSouleiman Fadal
62
edited Nov 21 '18 at 9:11
Armali
7,020936100
asked Nov 20 '18 at 20:16
Souleiman FadalSouleiman Fadal
62
edited Nov 21 '18 at 9:11
Armali
7,020936100
edited Nov 21 '18 at 9:11
Armali
7,020936100
edited Nov 21 '18 at 9:11
Armali
7,020936100
7,020936100
asked Nov 20 '18 at 20:16
Souleiman FadalSouleiman Fadal
62
asked Nov 20 '18 at 20:16
Souleiman FadalSouleiman Fadal
62
asked Nov 20 '18 at 20:16
Souleiman FadalSouleiman Fadal
62
62
1
You could have separate connecting tables for each possible owner, or restructure you database so that student, supervisor, and committee tables are all in one "users" table (and differentiated by a user type field); with optional student_details, staff_details, and/or committee_details tables for information unique to the different types.
– Uueerdo
Nov 20 '18 at 20:20
This might be a good start: stackoverflow.com/questions/7844460/…
– adam
Nov 20 '18 at 21:41
add a comment |
1
You could have separate connecting tables for each possible owner, or restructure you database so that student, supervisor, and committee tables are all in one "users" table (and differentiated by a user type field); with optional student_details, staff_details, and/or committee_details tables for information unique to the different types.
– Uueerdo
Nov 20 '18 at 20:20
This might be a good start: stackoverflow.com/questions/7844460/…
– adam
Nov 20 '18 at 21:41
1
1
You could have separate connecting tables for each possible owner, or restructure you database so that student, supervisor, and committee tables are all in one "users" table (and differentiated by a user type field); with optional student_details, staff_details, and/or committee_details tables for information unique to the different types.
– Uueerdo
Nov 20 '18 at 20:20
You could have separate connecting tables for each possible owner, or restructure you database so that student, supervisor, and committee tables are all in one "users" table (and differentiated by a user type field); with optional student_details, staff_details, and/or committee_details tables for information unique to the different types.
– Uueerdo
Nov 20 '18 at 20:20
This might be a good start: stackoverflow.com/questions/7844460/…
– adam
Nov 20 '18 at 21:41
This might be a good start: stackoverflow.com/questions/7844460/…
– adam
Nov 20 '18 at 21:41
add a comment |
1 Answer
1
active
oldest
votes
You are best using a polymorphic relationship.
https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations
Alternatively you could have a users table and have different roles for users using something like https://github.com/spatie/laravel-permission
answered Nov 20 '18 at 20:20
JoshJosh
720112
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53400866%2ffk-reference-multiple-tables-database-relations-and-foreign-key-constraints-in%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You are best using a polymorphic relationship.
https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations
Alternatively you could have a users table and have different roles for users using something like https://github.com/spatie/laravel-permission
answered Nov 20 '18 at 20:20
JoshJosh
720112
add a comment |
You are best using a polymorphic relationship.
https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations
Alternatively you could have a users table and have different roles for users using something like https://github.com/spatie/laravel-permission
answered Nov 20 '18 at 20:20
JoshJosh
720112
add a comment |
You are best using a polymorphic relationship.
https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations
Alternatively you could have a users table and have different roles for users using something like https://github.com/spatie/laravel-permission
answered Nov 20 '18 at 20:20
JoshJosh
720112
You are best using a polymorphic relationship.
https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations
Alternatively you could have a users table and have different roles for users using something like https://github.com/spatie/laravel-permission
answered Nov 20 '18 at 20:20
JoshJosh
720112
answered Nov 20 '18 at 20:20
JoshJosh
720112
answered Nov 20 '18 at 20:20
JoshJosh
720112
answered Nov 20 '18 at 20:20
JoshJosh
720112
720112
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53400866%2ffk-reference-multiple-tables-database-relations-and-foreign-key-constraints-in%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
You could have separate connecting tables for each possible owner, or restructure you database so that student, supervisor, and committee tables are all in one "users" table (and differentiated by a user type field); with optional student_details, staff_details, and/or committee_details tables for information unique to the different types.
– Uueerdo
Nov 20 '18 at 20:20
This might be a good start: stackoverflow.com/questions/7844460/…
– adam
Nov 20 '18 at 21:41