how to define primary key , forien key in loopback
up vote
0
down vote
favorite
I am creating an API through loopback and using visual database design tool MySQLworkbench.
While I'm creating models in loopback I confused to define keys(primary, foreign and candidate). When I go through loopback documentation it's said to use idInjection. But, I confused how to use it.
Please, anyone, give me guidance to solve this issue
mysql loopback
edited Nov 20 at 4:57
Sniffer
6341722
asked Nov 20 at 4:54
Arebhy Sri
33413
add a comment |
up vote
0
down vote
favorite
I am creating an API through loopback and using visual database design tool MySQLworkbench.
While I'm creating models in loopback I confused to define keys(primary, foreign and candidate). When I go through loopback documentation it's said to use idInjection. But, I confused how to use it.
Please, anyone, give me guidance to solve this issue
mysql loopback
edited Nov 20 at 4:57
Sniffer
6341722
asked Nov 20 at 4:54
Arebhy Sri
33413
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am creating an API through loopback and using visual database design tool MySQLworkbench.
While I'm creating models in loopback I confused to define keys(primary, foreign and candidate). When I go through loopback documentation it's said to use idInjection. But, I confused how to use it.
Please, anyone, give me guidance to solve this issue
mysql loopback
edited Nov 20 at 4:57
Sniffer
6341722
asked Nov 20 at 4:54
Arebhy Sri
33413
I am creating an API through loopback and using visual database design tool MySQLworkbench.
While I'm creating models in loopback I confused to define keys(primary, foreign and candidate). When I go through loopback documentation it's said to use idInjection. But, I confused how to use it.
Please, anyone, give me guidance to solve this issue
mysql loopback
mysql loopback
edited Nov 20 at 4:57
Sniffer
6341722
asked Nov 20 at 4:54
Arebhy Sri
33413
edited Nov 20 at 4:57
Sniffer
6341722
asked Nov 20 at 4:54
Arebhy Sri
33413
edited Nov 20 at 4:57
Sniffer
6341722
edited Nov 20 at 4:57
Sniffer
6341722
edited Nov 20 at 4:57
Sniffer
6341722
6341722
asked Nov 20 at 4:54
Arebhy Sri
33413
asked Nov 20 at 4:54
Arebhy Sri
33413
asked Nov 20 at 4:54
Arebhy Sri
33413
33413
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I'm afraid Loopback accept only "id" as primary key and it's mandatory to build loopback model relations.
The foreign key constraints or indexes setup in your database are not handeled by Loopback.
This job would belong to loopback-connector but it's not a part of the specifications.
The main advantages of working with loopback model relations is that you can have relations between different datasources. For example, when your create a "model A belongs to model B" relations, the datasource of model A can be different than the one of model B ! (and each datasource can use a different connector).
Sorry for my english...
Hope it helps
answered Nov 22 at 16:51
dun32
5714
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%2f53386460%2fhow-to-define-primary-key-forien-key-in-loopback%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
up vote
1
down vote
accepted
I'm afraid Loopback accept only "id" as primary key and it's mandatory to build loopback model relations.
The foreign key constraints or indexes setup in your database are not handeled by Loopback.
This job would belong to loopback-connector but it's not a part of the specifications.
The main advantages of working with loopback model relations is that you can have relations between different datasources. For example, when your create a "model A belongs to model B" relations, the datasource of model A can be different than the one of model B ! (and each datasource can use a different connector).
Sorry for my english...
Hope it helps
answered Nov 22 at 16:51
dun32
5714
add a comment |
up vote
1
down vote
accepted
I'm afraid Loopback accept only "id" as primary key and it's mandatory to build loopback model relations.
The foreign key constraints or indexes setup in your database are not handeled by Loopback.
This job would belong to loopback-connector but it's not a part of the specifications.
The main advantages of working with loopback model relations is that you can have relations between different datasources. For example, when your create a "model A belongs to model B" relations, the datasource of model A can be different than the one of model B ! (and each datasource can use a different connector).
Sorry for my english...
Hope it helps
answered Nov 22 at 16:51
dun32
5714
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I'm afraid Loopback accept only "id" as primary key and it's mandatory to build loopback model relations.
The foreign key constraints or indexes setup in your database are not handeled by Loopback.
This job would belong to loopback-connector but it's not a part of the specifications.
The main advantages of working with loopback model relations is that you can have relations between different datasources. For example, when your create a "model A belongs to model B" relations, the datasource of model A can be different than the one of model B ! (and each datasource can use a different connector).
Sorry for my english...
Hope it helps
answered Nov 22 at 16:51
dun32
5714
I'm afraid Loopback accept only "id" as primary key and it's mandatory to build loopback model relations.
The foreign key constraints or indexes setup in your database are not handeled by Loopback.
This job would belong to loopback-connector but it's not a part of the specifications.
The main advantages of working with loopback model relations is that you can have relations between different datasources. For example, when your create a "model A belongs to model B" relations, the datasource of model A can be different than the one of model B ! (and each datasource can use a different connector).
Sorry for my english...
Hope it helps
answered Nov 22 at 16:51
dun32
5714
answered Nov 22 at 16:51
dun32
5714
answered Nov 22 at 16:51
dun32
5714
answered Nov 22 at 16:51
dun32
5714
5714
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.
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%2fstackoverflow.com%2fquestions%2f53386460%2fhow-to-define-primary-key-forien-key-in-loopback%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
