You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: commands/eval.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,11 @@ These names of input keys are available to the script as the [_KEYS_ global runt
8
8
Any additional input arguments **should not** represent names of keys.
9
9
10
10
**Important:**
11
-
to ensure the correct execution of scripts, both in standalone and clustered deployments, all names of keys that a script accesses must be explicitly provided as input key arguments.
11
+
To ensure the correct execution of scripts, both in standalone and clustered deployments, all names of keys that a script accesses must be explicitly provided as input key arguments.
12
12
The script **should only** access keys whose names are given as input arguments.
13
13
Scripts **should never** access keys with programmatically-generated names or based on the contents of data structures stored in the database.
14
+
If a key with expiry (TTL) exists at the start of eval, it will not get expired during the evaluation of a script.
15
+
During the evaluation of a Lua script, TTL of a key can go down to zero. After that, it remains zero until the script terminates.
14
16
15
17
Please refer to the [Redis Programmability](/topics/programmability) and [Introduction to Eval Scripts](/topics/eval-intro) for more information about Lua scripts.
0 commit comments