Mixing
can not use sorted index in join query
I have a query:
SELECT pr."productId" FROM "ProductRecord" pr
INNER JOIN "ProductCategory" pc on pr."productId" = pc."productId"
WHERE pc."category" = ? AND pc."language" = ?
ORDER BY pr."dailyRock" DESC `
There is a descending ordered index on field dailyRock but since productId index is used on join the sorted index can not be used and everytime the aggregated result is needed to be sorted.
Can I force ignite to use both productId index and dailyRock index of ProductRecord table in the query above?
ignite
edited Jan 2 at 8:49
Stephen Darlington
46.1k995143
asked Jan 2 at 8:26
Ayberk CanseverAyberk Cansever
32
add a comment |
I have a query:
SELECT pr."productId" FROM "ProductRecord" pr
INNER JOIN "ProductCategory" pc on pr."productId" = pc."productId"
WHERE pc."category" = ? AND pc."language" = ?
ORDER BY pr."dailyRock" DESC `
There is a descending ordered index on field dailyRock but since productId index is used on join the sorted index can not be used and everytime the aggregated result is needed to be sorted.
Can I force ignite to use both productId index and dailyRock index of ProductRecord table in the query above?
ignite
edited Jan 2 at 8:49
Stephen Darlington
46.1k995143
asked Jan 2 at 8:26
Ayberk CanseverAyberk Cansever
32
add a comment |
I have a query:
SELECT pr."productId" FROM "ProductRecord" pr
INNER JOIN "ProductCategory" pc on pr."productId" = pc."productId"
WHERE pc."category" = ? AND pc."language" = ?
ORDER BY pr."dailyRock" DESC `
There is a descending ordered index on field dailyRock but since productId index is used on join the sorted index can not be used and everytime the aggregated result is needed to be sorted.
Can I force ignite to use both productId index and dailyRock index of ProductRecord table in the query above?
ignite
edited Jan 2 at 8:49
Stephen Darlington
46.1k995143
asked Jan 2 at 8:26
Ayberk CanseverAyberk Cansever
32
I have a query:
SELECT pr."productId" FROM "ProductRecord" pr
INNER JOIN "ProductCategory" pc on pr."productId" = pc."productId"
WHERE pc."category" = ? AND pc."language" = ?
ORDER BY pr."dailyRock" DESC `
There is a descending ordered index on field dailyRock but since productId index is used on join the sorted index can not be used and everytime the aggregated result is needed to be sorted.
Can I force ignite to use both productId index and dailyRock index of ProductRecord table in the query above?
ignite
ignite
edited Jan 2 at 8:49
Stephen Darlington
46.1k995143
asked Jan 2 at 8:26
Ayberk CanseverAyberk Cansever
32
edited Jan 2 at 8:49
Stephen Darlington
46.1k995143
asked Jan 2 at 8:26
Ayberk CanseverAyberk Cansever
32
edited Jan 2 at 8:49
Stephen Darlington
46.1k995143
edited Jan 2 at 8:49
Stephen Darlington
46.1k995143
edited Jan 2 at 8:49
Stephen Darlington
46.1k995143
46.1k995143
asked Jan 2 at 8:26
Ayberk CanseverAyberk Cansever
32
asked Jan 2 at 8:26
Ayberk CanseverAyberk Cansever
32
asked Jan 2 at 8:26
Ayberk CanseverAyberk Cansever
32
32
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
No, only one index per table may be used in each query.
You can try creating a composite index (dailyRock, productId) or (productId, dailyRock) although I'm not sure it'll help to avoid the sorting.
answered Jan 14 at 13:29
Stanislav LukyanovStanislav Lukyanov
1,136514
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%2f54003251%2fcan-not-use-sorted-index-in-join-query%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
No, only one index per table may be used in each query.
You can try creating a composite index (dailyRock, productId) or (productId, dailyRock) although I'm not sure it'll help to avoid the sorting.
answered Jan 14 at 13:29
Stanislav LukyanovStanislav Lukyanov
1,136514
add a comment |
No, only one index per table may be used in each query.
You can try creating a composite index (dailyRock, productId) or (productId, dailyRock) although I'm not sure it'll help to avoid the sorting.
answered Jan 14 at 13:29
Stanislav LukyanovStanislav Lukyanov
1,136514
add a comment |
No, only one index per table may be used in each query.
You can try creating a composite index (dailyRock, productId) or (productId, dailyRock) although I'm not sure it'll help to avoid the sorting.
answered Jan 14 at 13:29
Stanislav LukyanovStanislav Lukyanov
1,136514
No, only one index per table may be used in each query.
You can try creating a composite index (dailyRock, productId) or (productId, dailyRock) although I'm not sure it'll help to avoid the sorting.
answered Jan 14 at 13:29
Stanislav LukyanovStanislav Lukyanov
1,136514
answered Jan 14 at 13:29
Stanislav LukyanovStanislav Lukyanov
1,136514
answered Jan 14 at 13:29
Stanislav LukyanovStanislav Lukyanov
1,136514
answered Jan 14 at 13:29
Stanislav LukyanovStanislav Lukyanov
1,136514
1,136514
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%2f54003251%2fcan-not-use-sorted-index-in-join-query%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
