Defined in: packages/db/src/indexes/reverse-index.ts:4
TKey extends string | number
new ReverseIndex<TKey>(index): ReverseIndex<TKey>;Defined in: packages/db/src/indexes/reverse-index.ts:9
IndexInterface<TKey>
ReverseIndex<TKey>
get keyCount(): number;Defined in: packages/db/src/indexes/reverse-index.ts:55
number
IndexReader.keyCountget supportsRangeOptimization(): boolean;Defined in: packages/db/src/indexes/reverse-index.ts:47
Whether range lookups (gt/gte/lt/lte) on this index can be trusted to return every matching key. Range traversal relies on the index ordering, so it is unsafe when the index uses a custom comparator, whose order may not match the WHERE evaluator's relational operators. Callers must fall back to a full scan when this is false.
boolean
IndexReader.supportsRangeOptimizationcanOptimizeRangeFor(value): boolean;Defined in: packages/db/src/indexes/reverse-index.ts:51
Whether the live values in this index share the predicate operand's relational domain. Mixed domains can sort differently in the index and WHERE evaluator, which can make a range lookup omit matching rows.
unknown
boolean
IndexReader.canOptimizeRangeForlookup(operation, value): Set<TKey>;Defined in: packages/db/src/indexes/reverse-index.ts:15
"eq" | "gt" | "gte" | "lt" | "lte" | "in" | "like" | "ilike"
any
Set<TKey>
IndexReader.lookuprangeQuery(options): Set<TKey>;Defined in: packages/db/src/indexes/reverse-index.ts:29
Set<TKey>
IndexReader.rangeQuerysupports(operation): boolean;Defined in: packages/db/src/indexes/reverse-index.ts:43
"eq" | "gt" | "gte" | "lt" | "lte" | "in" | "like" | "ilike"
boolean
IndexReader.supportstake(
n,
from,
filterFn?): TKey[];Defined in: packages/db/src/indexes/reverse-index.ts:33
number
any
(key) => boolean
TKey[]
IndexReader.taketakeFromStart(n, filterFn?): TKey[];Defined in: packages/db/src/indexes/reverse-index.ts:37
number
(key) => boolean
TKey[]
IndexReader.takeFromStart