MsetCommand: Contents
MSET _key1_ _value1_ _key2_ _value2_ ... _keyN_ _valueN_ (Redis >
MSETNX _key1_ _value1_ _key2_ _value2_ ... _keyN_ _valueN_ (Redis >
MSET Return value
MSETNX Return value

# MsetCommand

ï»¿#sidebar StringCommandsSidebar

# MSET _key1_ _value1_ _key2_ _value2_ ... _keyN_ _valueN_ (Redis >

1.1) =

# MSETNX _key1_ _value1_ _key2_ _value2_ ... _keyN_ _valueN_ (Redis >

1.1) = Time complexity: O(1) to set every key

> Set the the respective keys to the respective values. MSET will replace oldvalues with new values, while MSETNX will not perform any operation at alleven if just a single key already exists.

> Because of this semantic MSETNX can be used in order to set different keysrepresenting different fields of an unique logic object in a way thatensures that either all the fields or none at all are set.

> Both MSET and MSETNX are atomic operations. This means that for instanceif the keys A and B are modified, another client talking to Redis can eithersee the changes to both A and B at once, or no modification at all.

## MSET Return value

Status code reply Basically +OK as MSET can't fail

## MSETNX Return value

Integer reply, specifically:

    1 if the all the keys were set
    0 if no key was set (at least one key already existed)