-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
HMSET under v4 doesn't work. HSET does #1746
Comments
// with an object
client.HSET('key', {
field1: 'value1',
field2: 'value2'
});
// with flat array
client.HSET('key', ['field1', 'value1', 'field2', 'value2']);
// with tuples
client.HSET('key', [['field1', 'value1'], ['field2', 'value2']]); for client.HMGET('key', ['field1', 'field2']); |
This might be the sort of thing to include/add to the migration guide perhaps? |
It is due to commands becoming camel case and if you were using a lower case like hset then you would hit this issue. Not the best way of releasing a new release. I was stuck on this too. |
Why then use the example with HMSET, this confused me. |
Your example doesn't work on 4.6.11, while there is an error of [ErrorReply: ERR wrong number of arguments for 'hset' command] |
HMSET does not seem to be supported
I have to resort to
sendcommand
instead?and
Results in
Additionally, after
HMGET can't get multiple keys?
results in
[ 'a' ]
Or is this a case of "node redis doesn't know about this yet" but it did in the last v3 version?
Environment:
The text was updated successfully, but these errors were encountered: