Skip to content
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

zrevrangestorebylex/zrevrangestorebyscore range arguments flipped #2203

Closed
mp911de opened this issue Sep 23, 2022 · 0 comments
Closed

zrevrangestorebylex/zrevrangestorebyscore range arguments flipped #2203

mp911de opened this issue Sep 23, 2022 · 0 comments
Labels
type: bug A general bug
Milestone

Comments

@mp911de
Copy link
Collaborator

mp911de commented Sep 23, 2022

Using the REV variant of ZREVRANGESTORE uses the lower bound as min and the upper bound as max. REV switches min/max semantics so the arguments are in wrong order.

@mp911de mp911de added the type: bug A general bug label Sep 23, 2022
@mp911de mp911de added this to the 6.2.1.RELEASE milestone Sep 23, 2022
mp911de added a commit that referenced this issue Sep 23, 2022
Flip the argument order to match REV min/max semantics where min is the upper bound and max the lower now.
mp911de added a commit that referenced this issue Sep 23, 2022
Flip the argument order to match REV min/max semantics where min is the upper bound and max the lower now.
@mp911de mp911de closed this as completed Sep 23, 2022
mp911de added a commit that referenced this issue Oct 7, 2022
Flip the argument order to match REV min/max semantics where min is the upper bound and max the lower now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant