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

add GETRANGE to Commands trait #202

Closed

Conversation

christian-blades-cb
Copy link
Contributor

@christian-blades-cb christian-blades-cb commented Mar 29, 2019

Adds

  • GETRANGE and SUBSTR (for redis versions < 2.0)
  • SETRANGE (redis versions >= 2.2.0)

@badboy
Copy link
Collaborator

badboy commented Apr 1, 2019

Let's ... not support Redis <2.0

@christian-blades-cb
Copy link
Contributor Author

@badboy Sounds good to me. Is there a redis version target for redis-rs that I should put add to the documentation? I could do that while I'm in there.

@badboy
Copy link
Collaborator

badboy commented Apr 2, 2019

Apparently AppVeyor comes with Redis 3.0, so technically that's what we can guarantee to support.

Copy link
Collaborator

@badboy badboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(just for visibility: let's not support old redis)

@badboy
Copy link
Collaborator

badboy commented Aug 26, 2019

Merged as 30d2008

@badboy badboy closed this Aug 26, 2019
barshaul pushed a commit to barshaul/redis-rs that referenced this pull request Jul 11, 2024
Node: Use new cluster creation script.
barshaul pushed a commit to barshaul/redis-rs that referenced this pull request Jul 11, 2024
…1276)

* Java: Add command `Zrangestore`. (Sorted Set Group) (redis-rs#202)

* Rebase + Spotless.

* Java: Add `Zinterstore` command.

* Rebase + Spotless.

* Minor IT test update.

* Minor documentation update.

* Minor IT comment update.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants