- ext
- redis
- redis.pl -- Redis client
- redis_server/3
- redis_connect/1
- redis_connect/3
- tls_verify/5
- sentinel_slave/4
- redis_disconnect/1
- redis_disconnect/2
- redis/2
- redis/3
- redis/1
- redis_write/2
- redis_read/2
- redis_get_list/3
- redis_get_list/4
- redis_set_list/3
- redis_get_hash/3
- redis_set_hash/3
- redis_array_dict/3
- redis_scan/3
- redis_sscan/4
- redis_hscan/4
- redis_zscan/4
- redis_current_command/2
- redis_current_command/3
- redis_property/2
- redis_subscribe/4
- redis_subscribe/2
- redis_unsubscribe/2
- redis_current_subscription/2
- redis_streams.pl -- Using Redis streams
- redis.pl -- Redis client
- redis
- redis_get_list(+Redis, +Key, -List) is det
- redis_get_list(+Redis, +Key, +ChunkSize, -List) is det
- Get the content of a Redis list in List. If ChunkSize is given and
smaller than the list length, List is returned as a lazy list. The
actual values are requested using redis
LRANGErequests. Note that this results in O(N^2) complexity. Using a lazy list is most useful for relatively short lists holding possibly large items.Note that values retrieved are strings, unless the value was added using
Term as prolog.It seems possible for
LLENto returnOK. I don't know why. As a work-around we return the empty list rather than an error.- See also
- - lazy_list/2 for a discussion on the difference between lazy lists and normal lists.