Attributes
Very Popular
Repository
Current version released
4 years ago
Dependencies
deno.land/x
Versions
- v0.32.4Latest
- v0.32.3
- v0.32.2
- v0.32.1
- v0.32.0
- v0.31.0
- v0.30.0
- v0.29.4
- v0.29.3
- v0.29.2
- v0.29.1
- v0.29.0
- v0.28.0
- v0.27.4
- v0.27.3
- v0.27.2
- v0.27.1
- v0.27.0
- v0.26.0
- v0.25.5
- v0.25.4
- v0.25.3
- v0.25.2
- v0.25.1
- v0.25.0
- v0.24.0
- v0.23.2
- v0.23.1
- v0.23.0
- v0.22.2
- v0.22.1
- v0.22.0
- v0.21.0
- v0.20.0
- v0.19.0
- v0.18.0
- v0.17.0
- v0.16.0
- v0.15.0
- v0.14.1
- v0.14.0
- v0.13.1
- v0.13.0
- v0.12.0
- v0.11.2
- v1.0.0-rc2
- v1.0.0-rc1
- v0.11.1
- v0.11.0
- v0.10.4
- v0.10.3
- v0.10.2
- v0.10.1
- v0.10.0
- v0.9.6
- v0.9.5
- v0.9.4
- v0.9.3
- v0.9.2
- v0.9.1
- v0.9.0
- v0.9.0-rc2
- v0.9.0-rc1
- v0.8.2
- v0.8.1
- v0.8.0
- v0.7.2
- v0.7.1
- v0.7.0
- v0.6.5
- v0.6.4
- v0.6.3
- v0.6.2
- v0.6.1
- v0.6.0
- v0.5.3
- v0.5.2
- v0.5.1
- v0.5.0
- v0.4.1
- v0.4.0
- v0.3.2
- v0.3.1
- v0.3.0
- v0.2.2
- v0.2.1
- v0.2.0
- v0.1.0
deno-redis
An experimental implementation of redis client for deno
Usage
needs --allow-net
privilege
Stateless Commands
import {connect} from "https://denopkg.com/keroxp/deno-redis/redis.ts"
const redis = await connect("127.0.0.1:6379");
const ok = await redis.set("hoge","fuga")
const fuga = await redis.get("hoge");
PubSub
const sub = await redis.subscribe("channel");
(async function() {
for await (const {channel, message} of sub.receive()) {
// on message
}
})()
Advanced Usage
Pipelining
https://redis.io/topics/pipelining
const redis = await connect("127.0.0.1:6379");
const pl = redis.pipeline();
await Promise.all([
pl.ping(),
pl.ping(),
pl.set("set1", "value1"),
pl.set("set2", "value2"),
pl.mget("set1", "set2"),
pl.del("set1"),
pl.del("set2")
]);
const replies = await pl.flush();
TxPipeline (pipeline with MULTI/EXEC)
We recommend to use tx()
instead of multi()/exec()
for transactional operation.MULTI/EXEC
are potentially stateful operation so that operation’s atomicity is guaranteed but redis’s state may change between MULTI and EXEC.
WATCH
is designed for these problems. You can ignore it by using TxPipeline because pipelined MULTI/EXEC commands are strictly executed in order at the time and no changes will happen during execution.
See detail https://redis.io/topics/transactions
const tx = redis.tx();
await Promise.all([
tx.set("a", "aa"),
tx.set("b", "bb"),
tx.del("c"),
])
await tx.flush();
// MULTI
// SET a aa
// SET b bb
// DEL c
// EXEC
Compatibility Table (5.0.3)
Connection
- AUTH
- ECHO
- PING
- QUIT
- SELECT
- SWAPDB
Keys
- DEL
- DUMP
- EXISTS
- EXPIRE
- EXPIREAT
- KEYS
- MIGRATE
- MOVE
- OBJECT
- PERSIST
- PEXPIRE
- PEXPIREAT
- PTTL
- RANDOMKEY
- RENAME
- RENAMENX
- RESTORE
- SORT
- TOUCH
- TTL
- TYPE
- UNLINK
- WAIT
- SCAN
String
- APPEND
- BITCOUNT
- BITFIELD
- BITOP
- BITPOS
- DECR
- DECRBY
- GET
- GETBIT
- GETRANGE
- GETSET
- INCR
- INCRBY
- INCRBYFLOAT
- MGET
- MSET
- MSETNX
- PSETEX
- SET
- SETBIT
- SETEX
- SETNX
- SETRANGE
- STRLEN
List
- BLPOP
- BRPOP
- BRPOPLPUSH
- LINDEX
- LINSERT
- LLEN
- LPOP
- LPUSH
- LPUSHX
- LRANGE
- LREM
- LSET
- LTRIM
- RPOP
- RPOPLPUSH
- RPUSH
- RPUSHX
Set
- SADD
- SCARD
- SDIFF
- SDIFFSTORE
- SINTER
- SINTERSTORE
- SISMEMBER
- SMEMBERS
- SMOVE
- SPOP
- SRANDMEMBER
- SREM
SortedSet
- BZPOPMIN
- BZPOPMAX
- ZADD
- ZCARD
- ZCOUNT
- ZINCRBY
- ZINTERSTORE
- ZLEXCOUNT
- ZPOPMAX
- ZPOPMIN
- ZRANGE
- ZRANGEBYLEX
- ZREVRANGEBYLEX
- ZRANGEBYSCORE
- ZRANK
- ZREM
- ZREMRANGEBYLEX
- ZREMRANGEBYRANK
- ZREMRANGEBYSCORE
- ZREVRANGE
- ZREVRANGEBYSCORE
- ZREVRANK
- ZSCORE
- ZUNIONSTORE
- ZSCAN
HashMap
- HDEL
- HEXISTS
- HGET
- HGETALL
- HINCRBY
- HINCRBYFLOAT
- HKEYS
- HLEN
- HMGET
- HMSET
- HSET
- HSETNX
- HSTRLEN
- HVALS
- HSCAN
GEO
- GEOADD
- GEOADD
- GEOHASH
- GEOPOS
- GEODIST
- GEORADIUS
- GEORADIUSBYMEMBER
Stream
WIP
Server
WIP
Cluster
None
HyperLogLog
- PFADD
- PFCOUNT
- PFMERGE
Multi
- MULTI
- EXEC
- DISCARD
- WATCH
- UNWATCH
PubSub
- PSUBSCRIBE
- PUBSUB
- PUBLISH
- PUNSUBSCRIBE
- SUBSCRIBE
- UNSUBSCRIBE
Scripting
- EVAL
- EVALSHA
- SCRIPT DEBUG
- SCRIPT EXISTS
- SCRIPT FLUSH
- SCRIPT KILL
- SCRIPT LOAD