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

Hset return value is not always correct #42

Open
cpjolicoeur opened this issue Mar 6, 2015 · 0 comments
Open

Hset return value is not always correct #42

cpjolicoeur opened this issue Mar 6, 2015 · 0 comments

Comments

@cpjolicoeur
Copy link

Reading the code for Hset, this package is comparing the return value to 1 to determine the bool return value.

According to the redis docs for HSET, a return value of 1 indicates a new field was added to the hash with the value given, while a return value of 0 means the given field was already in the hash and it's value was updated.

So a return of 0 or 1 both should indicate a successful return value, shouldn't it?

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

No branches or pull requests

1 participant