I want to look at the actual logic for Redis's HSET API as it seems like the HSET api in the rust crate is just a wrapper for:
However, there doesn't seem to be a deeper level/logic that explains how the value is cached into the hash?
The code for
cmd is here:
As you can see, when the "HSET" command is given, a new
Cmd struct is created. Subsequent calls to
.arg() will set arguments to this command:
Finally, to actually execute the command, a call to
execute() or similar is required:
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.