How to design db so that projects have many (invoice/quotes) which many orders
Currently, I have DB design where all of the orders belong, to customers, then orders have a lookup table to statuses (invoice/quote/draft).
I need to redesign it into a form where Customers have projects, each project may have multiple invoices/quotes that are linked to orders. But I am struggling to find out what is the best way to do it.
Because I work with existing data, I have limits to the number of changes I can do. But I need to be able to get projects from order table, as well as all related orders from invoices or proforma.
What form of relationship I should be creating in such scenario?
The closes that I found was polymorphic relation https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations is that the only way I can achieve that or there are more options?
database-design
asked Nov 22 '18 at 14:38
Andrius SolopovasAndrius Solopovas
314114
add a comment |
Currently, I have DB design where all of the orders belong, to customers, then orders have a lookup table to statuses (invoice/quote/draft).
I need to redesign it into a form where Customers have projects, each project may have multiple invoices/quotes that are linked to orders. But I am struggling to find out what is the best way to do it.
Because I work with existing data, I have limits to the number of changes I can do. But I need to be able to get projects from order table, as well as all related orders from invoices or proforma.
What form of relationship I should be creating in such scenario?
The closes that I found was polymorphic relation https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations is that the only way I can achieve that or there are more options?
database-design
asked Nov 22 '18 at 14:38
Andrius SolopovasAndrius Solopovas
314114
add a comment |
Currently, I have DB design where all of the orders belong, to customers, then orders have a lookup table to statuses (invoice/quote/draft).
I need to redesign it into a form where Customers have projects, each project may have multiple invoices/quotes that are linked to orders. But I am struggling to find out what is the best way to do it.
Because I work with existing data, I have limits to the number of changes I can do. But I need to be able to get projects from order table, as well as all related orders from invoices or proforma.
What form of relationship I should be creating in such scenario?
The closes that I found was polymorphic relation https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations is that the only way I can achieve that or there are more options?
database-design
asked Nov 22 '18 at 14:38
Andrius SolopovasAndrius Solopovas
314114
Currently, I have DB design where all of the orders belong, to customers, then orders have a lookup table to statuses (invoice/quote/draft).
I need to redesign it into a form where Customers have projects, each project may have multiple invoices/quotes that are linked to orders. But I am struggling to find out what is the best way to do it.
Because I work with existing data, I have limits to the number of changes I can do. But I need to be able to get projects from order table, as well as all related orders from invoices or proforma.
What form of relationship I should be creating in such scenario?
The closes that I found was polymorphic relation https://laravel.com/docs/5.7/eloquent-relationships#polymorphic-relations is that the only way I can achieve that or there are more options?
database-design
database-design
asked Nov 22 '18 at 14:38
Andrius SolopovasAndrius Solopovas
314114
asked Nov 22 '18 at 14:38
Andrius SolopovasAndrius Solopovas
314114
edited Nov 22 '18 at 14:48
Andrius Solopovas
asked Nov 22 '18 at 14:38
Andrius SolopovasAndrius Solopovas
314114
asked Nov 22 '18 at 14:38
Andrius SolopovasAndrius Solopovas
314114
asked Nov 22 '18 at 14:38
Andrius SolopovasAndrius Solopovas
314114
314114
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Usually, the project have a client (owner) and contractor(s) whereas invoices/orders is linked to customers. Hence you need to reuse the same entity in both roles: owner and customer.
I would suggest to add an entity like "Business party" or even "Legal entity" which may be linked to both "Project clients" and "Customers".
answered Nov 23 '18 at 13:39
sergeserge
69147
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%2f53433269%2fhow-to-design-db-so-that-projects-have-many-invoice-quotes-which-many-orders%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
Usually, the project have a client (owner) and contractor(s) whereas invoices/orders is linked to customers. Hence you need to reuse the same entity in both roles: owner and customer.
I would suggest to add an entity like "Business party" or even "Legal entity" which may be linked to both "Project clients" and "Customers".
answered Nov 23 '18 at 13:39
sergeserge
69147
add a comment |
Usually, the project have a client (owner) and contractor(s) whereas invoices/orders is linked to customers. Hence you need to reuse the same entity in both roles: owner and customer.
I would suggest to add an entity like "Business party" or even "Legal entity" which may be linked to both "Project clients" and "Customers".
answered Nov 23 '18 at 13:39
sergeserge
69147
add a comment |
Usually, the project have a client (owner) and contractor(s) whereas invoices/orders is linked to customers. Hence you need to reuse the same entity in both roles: owner and customer.
I would suggest to add an entity like "Business party" or even "Legal entity" which may be linked to both "Project clients" and "Customers".
answered Nov 23 '18 at 13:39
sergeserge
69147
Usually, the project have a client (owner) and contractor(s) whereas invoices/orders is linked to customers. Hence you need to reuse the same entity in both roles: owner and customer.
I would suggest to add an entity like "Business party" or even "Legal entity" which may be linked to both "Project clients" and "Customers".
answered Nov 23 '18 at 13:39
sergeserge
69147
answered Nov 23 '18 at 13:39
sergeserge
69147
answered Nov 23 '18 at 13:39
sergeserge
69147
answered Nov 23 '18 at 13:39
sergeserge
69147
69147
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%2f53433269%2fhow-to-design-db-so-that-projects-have-many-invoice-quotes-which-many-orders%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
