New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce multi directional iterators #3309
Comments
kostja
added
bug
Something isn't working
and removed
feature
A new functionality
labels
Nov 19, 2018
kyukhin
added
feature
A new functionality
and removed
prio1
bug
Something isn't working
labels
Mar 11, 2019
SudoBobo
added a commit
that referenced
this issue
Mar 11, 2019
Without multi-directional iterators (to be introduced in #3309) in most cases (except those when internal VDBE merge sorter is used) ORDER BY with different specified ordered leads to wrong result. So for now (till #3309 is resolved) different sort orders are forbidden. Close #4038 @TarantoolBot document Title: different sorting orders in ORDER BY are forbidden now The error will be raised if different sorting orders are encountered.
SudoBobo
added a commit
that referenced
this issue
Mar 11, 2019
Without multi-directional iterators (to be introduced in #3309) in most cases (except those when internal VDBE merge sorter is used) ORDER BY with different specified ordered leads to wrong result. So for now (till #3309 is resolved) different sort orders are forbidden. Close #4038 @TarantoolBot document Title: different sorting orders in ORDER BY are forbidden now The error will be raised if different sorting orders are encountered.
SudoBobo
added a commit
that referenced
this issue
Mar 15, 2019
Without multi-directional iterators (to be introduced in #3309) ORDER BY + LIMIT with different specified ordered leads to wrong result. So for now (till #3309 is resolved) different sort orders are forbidden in ORDER BY + LIMIT. Close #4038 @TarantoolBot document Title: different sorting orders in ORDER BY are forbidden now The error will be raised if different sorting orders are encountered.
As a temporary solution, we have banned different sorting orders in ORDER BY + LIMIT (#4038). Here are the tests which should be uncommented when the problem with ORDER BY + LIMIT would be solved: |
SudoBobo
added a commit
that referenced
this issue
Mar 15, 2019
Without multi-directional iterators (to be introduced in #3309) ORDER BY + LIMIT with different specified ordered leads to wrong result. So for now (till #3309 is resolved) different sort orders are forbidden in ORDER BY + LIMIT. Close #4038 @TarantoolBot document Title: different sorting orders in ORDER BY are forbidden now The error will be raised if different sorting orders are encountered.
SudoBobo
added a commit
that referenced
this issue
Mar 15, 2019
Without multi-directional iterators (to be introduced in #3309) ORDER BY + LIMIT with different specified ordered leads to wrong result. So for now (till #3309 is resolved) different sort orders are forbidden in ORDER BY + LIMIT. Close #4038 @TarantoolBot document Title: different sorting orders in ORDER BY are forbidden now The error will be raised if different sorting orders are encountered.
SudoBobo
added a commit
that referenced
this issue
Mar 15, 2019
Without multi-directional iterators (to be introduced in #3309) ORDER BY + LIMIT with different specified ordered leads to wrong result. So for now (till #3309 is resolved) different sort orders are forbidden in ORDER BY + LIMIT. Close #4038 @TarantoolBot document Title: different sorting orders in ORDER BY are forbidden now The error will be raised if different sorting orders are encountered.
SudoBobo
added a commit
that referenced
this issue
Mar 18, 2019
Without multi-directional iterators (to be introduced in #3309) ORDER BY + LIMIT with different specified ordered leads to wrong result. So for now (till #3309 is resolved) different sort orders are forbidden in ORDER BY + LIMIT. Close #4038 @TarantoolBot document Title: different sorting orders in ORDER BY are forbidden now The error will be raised if different sorting orders are encountered.
kyukhin
pushed a commit
that referenced
this issue
Mar 19, 2019
Without multi-directional iterators (to be introduced in #3309) ORDER BY + LIMIT with different specified ordered leads to wrong result. So for now (till #3309 is resolved) different sort orders are forbidden in ORDER BY + LIMIT. Close #4038 @TarantoolBot document Title: different sorting orders in ORDER BY are forbidden now The error will be raised if different sorting orders are encountered.
ImeevMA
added a commit
to ImeevMA/tarantool
that referenced
this issue
Feb 18, 2022
This patch allows LIMIT to be used with a different sort order in ORDER BY. This is a temporary solution and should be changed after issue tarantool#3309 is fixed. Closes tarantool#6664
ImeevMA
added a commit
to ImeevMA/tarantool
that referenced
this issue
Feb 18, 2022
This patch allows LIMIT to be used with a different sort order in ORDER BY. This is a temporary solution and should be changed after issue tarantool#3309 is fixed. Closes tarantool#6664
ImeevMA
added a commit
to ImeevMA/tarantool
that referenced
this issue
Feb 18, 2022
This patch allows LIMIT to be used with a different sort order in ORDER BY. This is a temporary solution and should be changed after issue tarantool#3309 is fixed. NO_DOC=It is fix of existing feature Closes tarantool#6664
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To process SQL queries like this:
Multi directional iterators are needed: we need to be able to specify ASC/DESC
order for each field.
The text was updated successfully, but these errors were encountered: