mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-08-28 10:54:59 +00:00
2b88d278bc
The PQL looks like: ``` Range(frame=f, field0 >< [200,610]) ``` One thing I noticed while implementing this is that it doesn't seem like `FieldRange()` is used in either `Frame` or `View`; the Executor calls `Fragment.FieldRange()` directly. The problem with this is that the offset logic is calculated in the Frame, but since the Executor doesn't go through Frame, then the Executor also has to calculate the offset before calling `Fragment.FieldRange`. We should unify this logic somewhere. Note, this applies to both `FieldRange` and `FieldRangeBetween`. |
||
|---|---|---|
| .. | ||
| ast.go | ||
| ast_test.go | ||
| doc.go | ||
| parser.go | ||
| parser_test.go | ||
| scanner.go | ||
| scanner_test.go | ||
| token.go | ||