diff options
author | Angus Pearson <angus@toaster.cc> | 2019-05-22 16:39:04 +0100 |
---|---|---|
committer | Angus Pearson <angus@toaster.cc> | 2019-05-22 16:39:04 +0100 |
commit | bf963253ecfd367b49081a26c1b5c410558aecfc (patch) | |
tree | b2f5e6bf499aca568bd9c10cbd72c7a7c402ed41 /src/t_set.c | |
parent | fd0ee469ab165d0e005e9fe1fca1c4f5c604cd56 (diff) | |
download | redis-bf963253ecfd367b49081a26c1b5c410558aecfc.tar.gz |
Implement `SCAN cursor [TYPE type]` modifier suggested in issue #6107.
Add tests to check basic functionality of this optional keyword, and also tested with
a module (redisgraph). Checked quickly with valgrind, no issues.
Copies name the type name canonicalisation code from `typeCommand`, perhaps this would
be better factored out to prevent the two diverging and both needing to be edited to
add new `OBJ_*` types, but this is a little fiddly with C strings.
The [redis-doc](https://github.com/antirez/redis-doc/blob/master/commands.json) repo
will need to be updated with this new arg if accepted.
A quirk to be aware of here is that the GEO commands are backed by zsets not their own
type, so they're not distinguishable from other zsets.
Additionally, for sparse types this has the same behaviour as `MATCH` in that it may
return many empty results before giving something, even for large `COUNT`s.
Diffstat (limited to 'src/t_set.c')
0 files changed, 0 insertions, 0 deletions