Have multiple foreign keys or one
I have 3 table:
brand: brand_id(pk), name
product: product_id(pk), name
brand_product: brand_product_id(pk), brand_id, product_id
And I have a report table, at the moment it looks like this:
product_report: product_report_id(pk), quantity, brand_id, product_id
My question is, what are the pros and cons of having the brand_product_id column instead of brand_id, product_id.
postgresql postgresql-9.3
asked Oct 14 '14 at 8:58
RockNinjaRockNinja
3053920
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have 3 table:
brand: brand_id(pk), name
product: product_id(pk), name
brand_product: brand_product_id(pk), brand_id, product_id
And I have a report table, at the moment it looks like this:
product_report: product_report_id(pk), quantity, brand_id, product_id
My question is, what are the pros and cons of having the brand_product_id column instead of brand_id, product_id.
postgresql postgresql-9.3
asked Oct 14 '14 at 8:58
RockNinjaRockNinja
3053920
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have 3 table:
brand: brand_id(pk), name
product: product_id(pk), name
brand_product: brand_product_id(pk), brand_id, product_id
And I have a report table, at the moment it looks like this:
product_report: product_report_id(pk), quantity, brand_id, product_id
My question is, what are the pros and cons of having the brand_product_id column instead of brand_id, product_id.
postgresql postgresql-9.3
asked Oct 14 '14 at 8:58
RockNinjaRockNinja
3053920
I have 3 table:
brand: brand_id(pk), name
product: product_id(pk), name
brand_product: brand_product_id(pk), brand_id, product_id
And I have a report table, at the moment it looks like this:
product_report: product_report_id(pk), quantity, brand_id, product_id
My question is, what are the pros and cons of having the brand_product_id column instead of brand_id, product_id.
postgresql postgresql-9.3
postgresql postgresql-9.3
asked Oct 14 '14 at 8:58
RockNinjaRockNinja
3053920
asked Oct 14 '14 at 8:58
RockNinjaRockNinja
3053920
asked Oct 14 '14 at 8:58
RockNinjaRockNinja
3053920
asked Oct 14 '14 at 8:58
RockNinjaRockNinja
3053920
asked Oct 14 '14 at 8:58
RockNinjaRockNinja
3053920
3053920
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In my opinion the pros are:
- when using queries, you can select a specific row inside brand_product, by only using brand_product_id.
- if you want another table, connected to the brand_product table, you can specify the rows by just using the brand_product_id rather than the combination of brand_id and product_id (though, it's rare to connect a third table to a junction table like brand_product, but not impossible. I did it in my previous project)
cons:
- you can have a row with the same brand_id and product_id combination multiple times (but you can solve this by creating a unique index on the product_id and brand_id columns).
So it's not a bad idea to have a brand_product_id.
answered Oct 14 '14 at 9:43
Erik van de VenErik van de Ven
386316
add a comment |
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
});
}
});
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%2f80115%2fhave-multiple-foreign-keys-or-one%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
In my opinion the pros are:
- when using queries, you can select a specific row inside brand_product, by only using brand_product_id.
- if you want another table, connected to the brand_product table, you can specify the rows by just using the brand_product_id rather than the combination of brand_id and product_id (though, it's rare to connect a third table to a junction table like brand_product, but not impossible. I did it in my previous project)
cons:
- you can have a row with the same brand_id and product_id combination multiple times (but you can solve this by creating a unique index on the product_id and brand_id columns).
So it's not a bad idea to have a brand_product_id.
answered Oct 14 '14 at 9:43
Erik van de VenErik van de Ven
386316
add a comment |
In my opinion the pros are:
- when using queries, you can select a specific row inside brand_product, by only using brand_product_id.
- if you want another table, connected to the brand_product table, you can specify the rows by just using the brand_product_id rather than the combination of brand_id and product_id (though, it's rare to connect a third table to a junction table like brand_product, but not impossible. I did it in my previous project)
cons:
- you can have a row with the same brand_id and product_id combination multiple times (but you can solve this by creating a unique index on the product_id and brand_id columns).
So it's not a bad idea to have a brand_product_id.
answered Oct 14 '14 at 9:43
Erik van de VenErik van de Ven
386316
add a comment |
In my opinion the pros are:
- when using queries, you can select a specific row inside brand_product, by only using brand_product_id.
- if you want another table, connected to the brand_product table, you can specify the rows by just using the brand_product_id rather than the combination of brand_id and product_id (though, it's rare to connect a third table to a junction table like brand_product, but not impossible. I did it in my previous project)
cons:
- you can have a row with the same brand_id and product_id combination multiple times (but you can solve this by creating a unique index on the product_id and brand_id columns).
So it's not a bad idea to have a brand_product_id.
answered Oct 14 '14 at 9:43
Erik van de VenErik van de Ven
386316
In my opinion the pros are:
- when using queries, you can select a specific row inside brand_product, by only using brand_product_id.
- if you want another table, connected to the brand_product table, you can specify the rows by just using the brand_product_id rather than the combination of brand_id and product_id (though, it's rare to connect a third table to a junction table like brand_product, but not impossible. I did it in my previous project)
cons:
- you can have a row with the same brand_id and product_id combination multiple times (but you can solve this by creating a unique index on the product_id and brand_id columns).
So it's not a bad idea to have a brand_product_id.
answered Oct 14 '14 at 9:43
Erik van de VenErik van de Ven
386316
answered Oct 14 '14 at 9:43
Erik van de VenErik van de Ven
386316
answered Oct 14 '14 at 9:43
Erik van de VenErik van de Ven
386316
answered Oct 14 '14 at 9:43
Erik van de VenErik van de Ven
386316
386316
add a comment |
add a comment |
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.
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%2f80115%2fhave-multiple-foreign-keys-or-one%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
