mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-20 10:42:26 +00:00
docs: clean up prose flagged by the shared Vale rules (#4596)
The existing docs have 254 findings from our shared Vale rules. Contributors would otherwise inherit these when editing the same lines. Clean up the prose across 80 pages: correct product names and a repeated word, simplify a few phrases, and replace dashes with punctuation that fits each sentence. The pinned Vale scan now reports zero findings, with no suppressions.
This commit is contained in:
@@ -14,9 +14,9 @@ plus what Lance adds.
|
||||
|
||||
| | |
|
||||
| --- | --- |
|
||||
| [Scalar functions](/sql/scalar-functions) | per row — math, string, regex, date/time, array, struct, JSON |
|
||||
| [Aggregate functions](/sql/dql/aggregation#functions) | per group — `count`, `sum`, statistical, approximate |
|
||||
| [Window functions](/sql/dql/window#functions) | per window — ranking, offset, running aggregates |
|
||||
| [Scalar functions](/sql/scalar-functions) | per row: math, string, regex, date/time, array, struct, JSON |
|
||||
| [Aggregate functions](/sql/dql/aggregation#functions) | per group: `count`, `sum`, statistical, approximate |
|
||||
| [Window functions](/sql/dql/window#functions) | per window: ranking, offset, running aggregates |
|
||||
| [Table functions](#table-functions) | produce a relation rather than a value |
|
||||
|
||||
<Note>
|
||||
@@ -51,7 +51,7 @@ and multi-match queries use this JSON encoding.
|
||||
|
||||
Its schema contains the dataset's columns plus `_score`, so every stored
|
||||
column is available in the result. Projections push into the scan.
|
||||
Being a relation is also what makes it compose — join it, filter it, aggregate
|
||||
Being a relation is also what makes it compose: join it, filter it, aggregate
|
||||
over it. This join additionally requires `my_docs.category_id` and a
|
||||
`categories` table with `id` and `name` columns:
|
||||
|
||||
@@ -73,7 +73,7 @@ multi-match query forms.
|
||||
### `_score` {#score}
|
||||
|
||||
A pseudo-column produced by `fts()`, carrying relevance for the row. It behaves
|
||||
like any other column — order by it, filter on it, project it — and exists only
|
||||
like any other column (order by it, filter on it, project it) and exists only
|
||||
in a relation that came from `fts()`. See
|
||||
[Data types](/sql/data-types#pseudo-columns).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user