added mset, mget

Author: amirreza8002

docs/source/commands/valkey_native_commands.rst

@@ -30,6 +30,31 @@ behaves in the same way as django backend contract specifies:
     cache.set("key", "value", timeout=None)
 
 
+Get and Set in bulk
+*******************
+
+django-valkey has two different kind of method for bulk get/set: atomic and non-atomic.
+
+atomic operations are done with ``mget()`` and ``mset()``
+
+.. code-block:: pycon
+
+    >>> from django.core.cache import cache
+    >>> cache.mset({"a": 1, "b": 2})
+    >>> cache.mget(["a", "b"])
+    {"a": 1, "b": 2}
+
+the non atomic operations are done with ``get_many()`` and ``set_many()``doen
+
+.. code-block:: pycon
+
+    >>> from django.core.cache import cache
+    >>> cache.set_many({"a": 1, "b": 2})
+    >>> cache.get_many(["a", "b"])
+    {"a": 1, "b": 2}
+
+**Note**: django-redis users should note that in django redis ``get_many()`` is an atomic operation, but ``set_many()``  is non-atomic.
+
 Scan and Delete in bulk
 ***********************
 

docs/source/migration.rst

@@ -34,6 +34,14 @@ you can easily fix this by running this commands:
 where settings.py is the file you have your configs in, change the file name if you are using a different name.
 
 
+Different commands
+##################
+
+in django-redis, ``get_many()`` is an atomic operation, but ``set_many()`` is non-atomic.
+
+in django-valkey ``mget()`` and ``mset()`` are atomic, and ``get_many()`` and ``set_many()`` are non-atomic.
+
+
 More options
 ############