table.between(lowerKey, upperKey) → selection
Get all documents between two keys. Accepts three optArgs:
index is set to the name of a secondary index,
between will return all documents where that index’s value is in the specified range (it uses the primary key by default).
right_bound may be set to
closed to indicate whether or not to include that endpoint of the range (by default,
left_bound is closed and
right_bound is open).
You may also use the special constants
r.maxval for boundaries, which represent “less than any index key” and “more than any index key” respectively. For instance, if you use
r.minval as the lower key, then
between will return all documents whose primary keys (or indexes) are less than the specified upper key.
If you use arrays as indexes (compound indexes), they will be sorted using lexicographical order. Take the following range as an example:
[[1, "c"] ... [5, "e"]]
This range includes all compound keys:
Example: Find all users with primary key >= 10 and < 20 (a normal half-open interval).
Example: Find all users with primary key >= 10 and <= 20 (an interval closed on both sides).
r.table("marvel").between(10, 20).optArg("right_bound", "closed").run(conn);
Example: Find all users with primary key < 20.
Example: Find all users with primary key > 10.
r.table("marvel").between(10, r.maxval()).optArg("left_bound", "open").run(conn);
Example: Between can be used on secondary indexes too. Just pass an optional index argument giving the secondary index to query.
r.table("dc").between("dark_knight", "man_of_steel").optArg("index", "code_name").run(conn);
Example: Get all users whose full name is between “John Smith” and “Wade Welles.”
r.table("users").between(r.array("Smith", "John"), r.array("Welles", "Wade")).optArg("index", "full_name").run(conn);
Note: Between works with secondary indexes on date fields, but will not work with unindexed date fields. To test whether a date value is between two other dates, use the during command, not
Secondary indexes can be used in extremely powerful ways with
between and other commands; read the full article on secondary indexes for examples using boolean operations,
contains and more.
Note: RethinkDB uses byte-wise ordering for
between and does not support Unicode collations; non-ASCII characters will be sorted by UTF-8 codepoint.
Note: If you chain
between after orderBy, the
between command must use the index specified in
orderBy, and will default to that index. Trying to specify another index will result in a
Couldn't find what you were looking for?
© RethinkDB contributors
Licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License.