-
Notifications
You must be signed in to change notification settings - Fork 2
Lots of changes for Redis & MySQL #8
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @harshadptl,
Thank you for this pull-request.
I had couple of concerns and wanted to know your opinions.
- Do we need Sismembers?. Just like Sadd, we can use Sismember to work with multiple keys IMO.
- Instead of returning NoImplemented error, wouldnt it be useful if we could use "get" or any other workaround to check membership?.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Thats a good idea
- Didn't get your point
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For 2. Instead of returning this "errors.New("mantle: SETS/Sismember unimplemented for memcache datastore")", we can do a get(key) and check if it exists. NotImpleted error is not so useful IMO.
This reverts commit 6d9ce85.
No description provided.