Db Design: Junction table or column












1















I have three tables like below.



user        company     user_company
-------- ------- ------------------
id(pk) id(pk) user_id(pk, fk)
company_id(pk, fk)


My problem is: Each user and company, must have a unique customer number. And I want to connect these user and company tables to single table.



So, should I create junction tables for user and company?



customer            user_customer           company_customer
--------------- ------------------ ----------------
customer_no(pk) user_id(pk, fk) company_id(pk, fk)
customer_type customer_no(pk, fk) customer_no(pk, fk)


Or should I just add id column to customer table?



customer
---------------
customer_no(pk)
user_id(fk)
company_id(fk)


Which one is correct? Or, is there any other way to do this?









share







New contributor




mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • I'd keep it simple and just add the id to the customer table unless you have a very good reason not to.

    – Mr.Brownstone
    32 secs ago
















1















I have three tables like below.



user        company     user_company
-------- ------- ------------------
id(pk) id(pk) user_id(pk, fk)
company_id(pk, fk)


My problem is: Each user and company, must have a unique customer number. And I want to connect these user and company tables to single table.



So, should I create junction tables for user and company?



customer            user_customer           company_customer
--------------- ------------------ ----------------
customer_no(pk) user_id(pk, fk) company_id(pk, fk)
customer_type customer_no(pk, fk) customer_no(pk, fk)


Or should I just add id column to customer table?



customer
---------------
customer_no(pk)
user_id(fk)
company_id(fk)


Which one is correct? Or, is there any other way to do this?









share







New contributor




mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • I'd keep it simple and just add the id to the customer table unless you have a very good reason not to.

    – Mr.Brownstone
    32 secs ago














1












1








1








I have three tables like below.



user        company     user_company
-------- ------- ------------------
id(pk) id(pk) user_id(pk, fk)
company_id(pk, fk)


My problem is: Each user and company, must have a unique customer number. And I want to connect these user and company tables to single table.



So, should I create junction tables for user and company?



customer            user_customer           company_customer
--------------- ------------------ ----------------
customer_no(pk) user_id(pk, fk) company_id(pk, fk)
customer_type customer_no(pk, fk) customer_no(pk, fk)


Or should I just add id column to customer table?



customer
---------------
customer_no(pk)
user_id(fk)
company_id(fk)


Which one is correct? Or, is there any other way to do this?









share







New contributor




mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I have three tables like below.



user        company     user_company
-------- ------- ------------------
id(pk) id(pk) user_id(pk, fk)
company_id(pk, fk)


My problem is: Each user and company, must have a unique customer number. And I want to connect these user and company tables to single table.



So, should I create junction tables for user and company?



customer            user_customer           company_customer
--------------- ------------------ ----------------
customer_no(pk) user_id(pk, fk) company_id(pk, fk)
customer_type customer_no(pk, fk) customer_no(pk, fk)


Or should I just add id column to customer table?



customer
---------------
customer_no(pk)
user_id(fk)
company_id(fk)


Which one is correct? Or, is there any other way to do this?







database-design





share







New contributor




mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










share







New contributor




mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








share



share






New contributor




mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 7 mins ago









mnesimimnesimi

6




6




New contributor




mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






mnesimi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • I'd keep it simple and just add the id to the customer table unless you have a very good reason not to.

    – Mr.Brownstone
    32 secs ago



















  • I'd keep it simple and just add the id to the customer table unless you have a very good reason not to.

    – Mr.Brownstone
    32 secs ago

















I'd keep it simple and just add the id to the customer table unless you have a very good reason not to.

– Mr.Brownstone
32 secs ago





I'd keep it simple and just add the id to the customer table unless you have a very good reason not to.

– Mr.Brownstone
32 secs ago










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
});


}
});






mnesimi is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227908%2fdb-design-junction-table-or-column%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








mnesimi is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















mnesimi is a new contributor. Be nice, and check out our Code of Conduct.













mnesimi is a new contributor. Be nice, and check out our Code of Conduct.












mnesimi 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227908%2fdb-design-junction-table-or-column%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

SQL Server 17 - Attemping to backup to remote NAS but Access is denied

Always On Availability groups resolving state after failover - Remote harden of transaction...

Restoring from pg_dump with foreign key constraints