Sequelize return a tree without sequelize-hierarchy
I can't find a way to return a tree with multples levels using just sequelize (without another module).
Sequelize-hierarchy resolve the problem, but is too much for me - add another table; return parent...
I need just list childrens.
An ugly solution would be to write include within include. But in this case, the levels would be limited.
bad way:
include: [
{
model: models.access_Resource,
as: 'children',
required: false,
include: [
{
model: models.access_Resource,
as: 'children',
required: false,
include: [
{
model: models.access_Resource,
as: 'children',
required: false
}
]
}
]
}
]
I came from the laravel and I solve this with only 3 lines. I believe that with node / sequelize is not different. But I can not find a solution.
Could someone help me, please?
##EDIT##
The fast solution, is create a helper to put include within include recursively.
const buildTreeIncludes = (model, level) => {
if (level > 0) {
return {
include: {
model,
as: 'children',
required: false,
...buildTreeIncludes(model, level-1)
}
}
} else {
return {};
}
}
export default buildTreeIncludes;
node.js sequelize.js
add a comment |
I can't find a way to return a tree with multples levels using just sequelize (without another module).
Sequelize-hierarchy resolve the problem, but is too much for me - add another table; return parent...
I need just list childrens.
An ugly solution would be to write include within include. But in this case, the levels would be limited.
bad way:
include: [
{
model: models.access_Resource,
as: 'children',
required: false,
include: [
{
model: models.access_Resource,
as: 'children',
required: false,
include: [
{
model: models.access_Resource,
as: 'children',
required: false
}
]
}
]
}
]
I came from the laravel and I solve this with only 3 lines. I believe that with node / sequelize is not different. But I can not find a solution.
Could someone help me, please?
##EDIT##
The fast solution, is create a helper to put include within include recursively.
const buildTreeIncludes = (model, level) => {
if (level > 0) {
return {
include: {
model,
as: 'children',
required: false,
...buildTreeIncludes(model, level-1)
}
}
} else {
return {};
}
}
export default buildTreeIncludes;
node.js sequelize.js
A few hours later, I decided to create a helper to create include within the include according to the pre-selected level. That way I maintain a good perfomance in the selection, with unknown levels, without having to use another library with the minimum of intervention in the code.
– rodrigoclp
Nov 26 '18 at 22:32
add a comment |
I can't find a way to return a tree with multples levels using just sequelize (without another module).
Sequelize-hierarchy resolve the problem, but is too much for me - add another table; return parent...
I need just list childrens.
An ugly solution would be to write include within include. But in this case, the levels would be limited.
bad way:
include: [
{
model: models.access_Resource,
as: 'children',
required: false,
include: [
{
model: models.access_Resource,
as: 'children',
required: false,
include: [
{
model: models.access_Resource,
as: 'children',
required: false
}
]
}
]
}
]
I came from the laravel and I solve this with only 3 lines. I believe that with node / sequelize is not different. But I can not find a solution.
Could someone help me, please?
##EDIT##
The fast solution, is create a helper to put include within include recursively.
const buildTreeIncludes = (model, level) => {
if (level > 0) {
return {
include: {
model,
as: 'children',
required: false,
...buildTreeIncludes(model, level-1)
}
}
} else {
return {};
}
}
export default buildTreeIncludes;
node.js sequelize.js
I can't find a way to return a tree with multples levels using just sequelize (without another module).
Sequelize-hierarchy resolve the problem, but is too much for me - add another table; return parent...
I need just list childrens.
An ugly solution would be to write include within include. But in this case, the levels would be limited.
bad way:
include: [
{
model: models.access_Resource,
as: 'children',
required: false,
include: [
{
model: models.access_Resource,
as: 'children',
required: false,
include: [
{
model: models.access_Resource,
as: 'children',
required: false
}
]
}
]
}
]
I came from the laravel and I solve this with only 3 lines. I believe that with node / sequelize is not different. But I can not find a solution.
Could someone help me, please?
##EDIT##
The fast solution, is create a helper to put include within include recursively.
const buildTreeIncludes = (model, level) => {
if (level > 0) {
return {
include: {
model,
as: 'children',
required: false,
...buildTreeIncludes(model, level-1)
}
}
} else {
return {};
}
}
export default buildTreeIncludes;
node.js sequelize.js
node.js sequelize.js
edited Nov 28 '18 at 16:31
rodrigoclp
asked Nov 26 '18 at 20:11
rodrigoclprodrigoclp
11
11
A few hours later, I decided to create a helper to create include within the include according to the pre-selected level. That way I maintain a good perfomance in the selection, with unknown levels, without having to use another library with the minimum of intervention in the code.
– rodrigoclp
Nov 26 '18 at 22:32
add a comment |
A few hours later, I decided to create a helper to create include within the include according to the pre-selected level. That way I maintain a good perfomance in the selection, with unknown levels, without having to use another library with the minimum of intervention in the code.
– rodrigoclp
Nov 26 '18 at 22:32
A few hours later, I decided to create a helper to create include within the include according to the pre-selected level. That way I maintain a good perfomance in the selection, with unknown levels, without having to use another library with the minimum of intervention in the code.
– rodrigoclp
Nov 26 '18 at 22:32
A few hours later, I decided to create a helper to create include within the include according to the pre-selected level. That way I maintain a good perfomance in the selection, with unknown levels, without having to use another library with the minimum of intervention in the code.
– rodrigoclp
Nov 26 '18 at 22:32
add a comment |
0
active
oldest
votes
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%2f53488332%2fsequelize-return-a-tree-without-sequelize-hierarchy%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
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%2f53488332%2fsequelize-return-a-tree-without-sequelize-hierarchy%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
A few hours later, I decided to create a helper to create include within the include according to the pre-selected level. That way I maintain a good perfomance in the selection, with unknown levels, without having to use another library with the minimum of intervention in the code.
– rodrigoclp
Nov 26 '18 at 22:32