This library is a client to Redis,
a popular key value store to deal with caching and communication between
In the typical use case we register the details of one or more Redis
servers using redis_server/3.
Subsequenly, redis/2-3 is used to
issue commands on the server. For example:
?- redis_server(default, redis:6379, [password("secret")]).
?- redis(default, set(user, "Bob")).
?- redis(default, get(user), User).
User = "Bob"
- Register a redis server without connecting to it. The ServerName
acts as a lazy connection alias. Initially the ServerName
localhost:6379 with no connect options. The
server is used for redis/1 and redis/2
and may be changed using this predicate. Options are
described with redis_connect/3.
Connections established this way are by default automatically
reconnected if the connection is lost for some reason unless a
reconnect(false) option is specified.
- Connect to a redis server. The main mode is
redis_connect(+Address, -Connection, +Options). redis_connect/1
is equivalent to
redis_connect(localhost:6379, Connection, ). Options:
true, try to reconnect to the service when the
connection seems lost. Default is
true for connections
for explictly opened connections.
specified, these are used to authenticate using the HELLO
- Authenticate using Password
- Specify the connection protocol version. Initially this is version 2.
Redis 6 also supports version 3. When specified as
3, the HELLO
command is used to upgrade the protocol.
- When specified, initiate a TLS connection. If this option is specified
we must also specify the
- CA Certificate file to verify with.
- Client certificate to authenticate with.
- Private key file to authenticate with.
- Used together with an Address of the form
to enable contacting a network of Redis servers guarded by a sentinel
- Authentication information for the senitels. When omitted we try to
connect withour authentication.
Instead of using these predicates, redis/2
and redis/3 are normally used with a server
name argument registered using redis_server/3.
These predicates are meant for creating a temporary paralel connection
or using a connection with a blocking call.
|Address ||is a term Host:Port, |
or the name of a server registered using redis_server/3.
The latter realises a new connection that is typically used for
blocking redis commands such as listening for published messages,
waiting on a list or stream.
redis_connect(-Connection, +Host, +Port) provides
compatibility to the original GNU-Prolog interface and is equivalent to
redis_connect(Host:Port, Connection, ).
+ProblemCert, +AllCerts, +FirstCert, +Status)
- Accept or reject the certificate verification. Similar to the Redis
command line client (
redis-cli), we accept the certificate
as long as it is signed, not verifying the hostname.
- Disconnect from a redis server. The second form takes one option,
similar to close/2:
false), do not raise any
Connection does not exist or closing the connection raises a
network or I/O related exception. This version is used internally if a
connection is in a broken state, either due to a protocol error or a
- This predicate is overloaded to handle two types of requests. First, it
is a shorthand for
redis(Connection, Command, _) and
second, it can be used to exploit Redis pipelines and transactions.
The second form is acticated if Request is a list. In
that case, each element of the list is either a term
Command -> Reply
or a simple
Command. Semantically this represents a sequence of redis/3
redis/2 calls. It differs in the
- All commands are sent in one batch, after which all replies are
read. This reduces the number of round trips and typically
greatly improves performance.
- If the first command is
multi and the last
the commands are executed as a Redis transaction, i.e., they are
- If one of the commands returns an error, the subsequent commands
are still executed.
- You can not use variables from commands earlier in the list for
commands later in the list as a result of the above execution order.
Procedurally, the process takes the following steps:
- Send all commands
- Read all replies and push messages
- Handle all callbacks from push messages
- Check whether one of the replies is an error. If so, raise this
error (subsequent errors are lost)
- Bind all replies for the
Command -> Reply terms.
lrange(li,0,-1) -> List
List = ["2", "1"].
- Execute a redis Command on Connnection. Next, bind Reply
to the returned result. Command is a callable term whose
functor is the name of the Redis command and whose arguments are
translated to Redis arguments according to the rules below. Note that
all text is always represented using UTF-8 encoding.
- Atomic values are emitted verbatim
- A term A:B:... where all arguments are either atoms, strings or
integers (no floats) is translated into a string
This is a common shorthand for representing Redis keys.
- A term Term as prolog is emitted as "
followed by Term in canonical form.
- Any other term is emitted as write/1.
Reply is either a plain term (often a variable) or a term
Value as Type.
In the latter form, Type dictates how the Redis bulk
reply is translated to Prolog. The default equals to
i.e., as a number of the content satisfies the Prolog number syntax and
as an atom otherwise.
status(Atom) Returned if the server replies with
Atom is the textual value of Status converted to lower case,
nil This atom is returned for a NIL/NULL value. Note
that if the reply is only
nil, redis/3 fails.
nil value may be embedded inside lists or maps.
- A number Returned if the server replies an integer (":Int"), double
(",Num") or big integer ("(Num")
- A string Returned on a bulk reply. Bulk replies are supposed
to be in UTF-8 encoding. The the bulk reply starts with "
it is supposed to be a Prolog term. Note that this intepretation means
it is not possible to read arbitrary binary blobs.
- A list of replies. A list may also contain
nil. If Reply
as a whole would be
nil the call fails.
- A list of pairs. This is returned for the redis version 3
protocol "%Map". Both the key and value respect the same rules as above.
Redis bulk replies are translated depending on the
as explained above.
- Create a SWI-Prolog string object interpreting the blob as following Encoding. Encoding
is a restricted set of SWI-Prolog's encodings:
text (the current locale translation).
- As above, producing an atom.
- As above, producing a list of integers (Unicode code points)
- As above, producing a list of one-character atoms.
- Interpret the bytes as a string representing a number. If the string
does not represent a number of the requested type a
- Same as integer, but demands the value to be between the Prolog flags
max_tagged_integer, allowing the value to be used as a
- Same as
- auto(AsText, AsNumber)
- If the bulk string confirms the syntax of AsNumber, convert
the value to the requested numberical type. Else convert the value to
text according to AsText. This is similar to the Prolog
- Alias for
auto(atom,tagged_integer). This allows the value
to be used as a key for a SWI-Prolog dict.
- pairs(AsKey, AsValue)
- Convert a map or array of even length into pairs for which the key
satisfies AsKey and the value AsValue. The
type can also be applied to a Redis array. In this case the array length
must be even. This notably allows fetching a Redis
hash as pairs using
HGETALL using version 2 of the
- dict(AsKey, AsValue)
- Similar to
pairs(AsKey, AsValue), but convert the resulting
pair list into a SWI-Prolog dict. AsKey must convert to a
valid dict key, i.e., an atom or tagged integer. See
- Shorthand for
Here are some simple examples
?- redis(default, set(a, 42), X).
X = status("OK").
?- redis(default, get(a), X).
X = "42".
?- redis(default, get(a), X as integer).
X = 42.
?- redis(default, get(a), X as float).
X = 42.0.
?- redis(default, set(swipl:version, 8)).
?- redis(default, incr(swipl:version), X).
X = 9.
- Connect to the default redis server, call redist/3
using Request, disconnect and print the result. This
predicate is intended for interactive usage.
- Write command and read replies from a Redis server. These are
building blocks for subscribing to event streams.
+Key, +ChunkSize, -List)
- 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
requests. Note that this results in O(N
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
Term as prolog.
- See also
- lazy_list/2 for a discussion on the
difference between lazy lists and normal lists.
- Associate a Redis key with a list. As Redis has no
concept of an empty list, if List is
is deleted. Note that key values are always strings in Redis.
The same conversion rules as for
- Put/get a Redis hash as a Prolog dict. Putting a dict first
Key. Note that in many cases applications will manage Redis
hashes by key. redis_get_hash/3
is notably a user friendly alternative to the Redis
command. If the Redis hash is not used by other (non-Prolog)
applications one may also consider using the
Term as prolog syntax to store the Prolog dict as-is.
- Translate a Redis reply representing hash data into a SWI-Prolog dict. Array
is either a list of alternating keys and values or a list of pairs.
When translating to an array, this is always a list of alternating keys
|Tag ||is the SWI-Prolog dict tag. |
+Set, -LazyList, +Options)
+Hash, -LazyList, +Options)
+Set, -LazyList, +Options)
- Map the Redis
and ZSCAN‘commands into a lazy list. For redis_scan/3
and redis_sscan/4 the result
is a list of strings. For redis_hscan/4
and redis_zscan/4, the result
is a list of pairs. Options processed:
- Adds the
MATCH subcommand, only returning matches for
- Adds the
COUNT subcommand, giving a hint to the size of the
- Adds the
TYPE subcommand, only returning answers of the
- See also
- True when Command has Properties. Fails if Command
is not defined. The redis_current_command/3
version returns the command argument specification. See Redis
documentation for an explanation.
- True if Property is a property of the Redis
server. Currently uses
redis(info, String) and parses the result. As this is for
machine usage, properties names *_human are skipped.
+Channels, -Id, +Options)
- Subscribe to one or more Redis PUB/SUB channels. This
predicate creates a thread using thread_create/3
with the given Options. Once running, the thread listens for
messages. The message content is a string or Prolog term as described in redis/3.
On receiving a message, the following message is broadcasted:
redis(Id, Channel, Data)
removes the last subscription, the thread terminates.
To simply print the incomming messages use e.g.
?- listen(redis(_, Channel, Data),
format('Channel ~p got ~p~n', [Channel,Data])).
?- redis_subscribe(default, test, Id, ).
Id = redis_pubsub_3,
?- redis(publish(test, "Hello world")).
Channel test got "Hello world"
|Id ||is the thread identifier of the listening
thread. Note that the Options |
alias(Name) can be
used to get a system wide name.
- Add/remove channels from for the subscription. If no subscriptions
remain, the listening thread terminates.
|Channels ||is either a single channel or a
list thereof. Each channel specification is either an atom or a term‘A:B:...`,
where all parts are atoms. |
- True when a PUB/SUB subscription with Id is listening on Channels.