Database Design - multiple tables
I am trying to build a database that has all of our employees, their skills, and the level of their skills. The idea is that a manager could go in, type in a skill, and relevant employees are returned.
I am finding that I am getting stuck on PK's and FK's - and really how to go about it altogether.
So far, I believe I need to create 3 tables (Employees, Skills that will be separated into 4 general areas, and Skill Level which will be 5 different options).
With that, I am at a loss for how I can connect them in a way that each employee can be attached with multiple skills that also shows at what level they're at.
Not necessarily looking for someone to do the work for me, but if someone can clarify whether or not this logic will work and how to get on track - I probably can research the sql code for it.
Thanks!
postgresql database-design foreign-key primary-key
New contributor
add a comment |
I am trying to build a database that has all of our employees, their skills, and the level of their skills. The idea is that a manager could go in, type in a skill, and relevant employees are returned.
I am finding that I am getting stuck on PK's and FK's - and really how to go about it altogether.
So far, I believe I need to create 3 tables (Employees, Skills that will be separated into 4 general areas, and Skill Level which will be 5 different options).
With that, I am at a loss for how I can connect them in a way that each employee can be attached with multiple skills that also shows at what level they're at.
Not necessarily looking for someone to do the work for me, but if someone can clarify whether or not this logic will work and how to get on track - I probably can research the sql code for it.
Thanks!
postgresql database-design foreign-key primary-key
New contributor
One way to look at it: There is a many-to-many relationship between employees and skills, and skill level is a property (attribute) of such relationship.
– mustaccio
42 mins ago
Hmmm - I forgot about that type of relationship (obviously novice!). I will start there and re-create my data model to reflect this..hopefully this gives me a better start. Thank you!
– Chanel Tapper
35 mins ago
add a comment |
I am trying to build a database that has all of our employees, their skills, and the level of their skills. The idea is that a manager could go in, type in a skill, and relevant employees are returned.
I am finding that I am getting stuck on PK's and FK's - and really how to go about it altogether.
So far, I believe I need to create 3 tables (Employees, Skills that will be separated into 4 general areas, and Skill Level which will be 5 different options).
With that, I am at a loss for how I can connect them in a way that each employee can be attached with multiple skills that also shows at what level they're at.
Not necessarily looking for someone to do the work for me, but if someone can clarify whether or not this logic will work and how to get on track - I probably can research the sql code for it.
Thanks!
postgresql database-design foreign-key primary-key
New contributor
I am trying to build a database that has all of our employees, their skills, and the level of their skills. The idea is that a manager could go in, type in a skill, and relevant employees are returned.
I am finding that I am getting stuck on PK's and FK's - and really how to go about it altogether.
So far, I believe I need to create 3 tables (Employees, Skills that will be separated into 4 general areas, and Skill Level which will be 5 different options).
With that, I am at a loss for how I can connect them in a way that each employee can be attached with multiple skills that also shows at what level they're at.
Not necessarily looking for someone to do the work for me, but if someone can clarify whether or not this logic will work and how to get on track - I probably can research the sql code for it.
Thanks!
postgresql database-design foreign-key primary-key
postgresql database-design foreign-key primary-key
New contributor
New contributor
New contributor
asked 1 hour ago
Chanel TapperChanel Tapper
1
1
New contributor
New contributor
One way to look at it: There is a many-to-many relationship between employees and skills, and skill level is a property (attribute) of such relationship.
– mustaccio
42 mins ago
Hmmm - I forgot about that type of relationship (obviously novice!). I will start there and re-create my data model to reflect this..hopefully this gives me a better start. Thank you!
– Chanel Tapper
35 mins ago
add a comment |
One way to look at it: There is a many-to-many relationship between employees and skills, and skill level is a property (attribute) of such relationship.
– mustaccio
42 mins ago
Hmmm - I forgot about that type of relationship (obviously novice!). I will start there and re-create my data model to reflect this..hopefully this gives me a better start. Thank you!
– Chanel Tapper
35 mins ago
One way to look at it: There is a many-to-many relationship between employees and skills, and skill level is a property (attribute) of such relationship.
– mustaccio
42 mins ago
One way to look at it: There is a many-to-many relationship between employees and skills, and skill level is a property (attribute) of such relationship.
– mustaccio
42 mins ago
Hmmm - I forgot about that type of relationship (obviously novice!). I will start there and re-create my data model to reflect this..hopefully this gives me a better start. Thank you!
– Chanel Tapper
35 mins ago
Hmmm - I forgot about that type of relationship (obviously novice!). I will start there and re-create my data model to reflect this..hopefully this gives me a better start. Thank you!
– Chanel Tapper
35 mins ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
Chanel Tapper is a new contributor. Be nice, and check out our Code of Conduct.
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%2fdba.stackexchange.com%2fquestions%2f226713%2fdatabase-design-multiple-tables%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Chanel Tapper is a new contributor. Be nice, and check out our Code of Conduct.
Chanel Tapper is a new contributor. Be nice, and check out our Code of Conduct.
Chanel Tapper is a new contributor. Be nice, and check out our Code of Conduct.
Chanel Tapper is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Database Administrators Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fdba.stackexchange.com%2fquestions%2f226713%2fdatabase-design-multiple-tables%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
One way to look at it: There is a many-to-many relationship between employees and skills, and skill level is a property (attribute) of such relationship.
– mustaccio
42 mins ago
Hmmm - I forgot about that type of relationship (obviously novice!). I will start there and re-create my data model to reflect this..hopefully this gives me a better start. Thank you!
– Chanel Tapper
35 mins ago