mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-13 14:16:54 +00:00
Jack YeandClaude Sonnet 5
de95ed3f6d
A broad documentation pass across the areas LanceDB Enterprise and Embedded diverge on most: **Data Curation** -- GPU Function execution, Slurm scheduling (and what Slurm is, for readers new to it), blob late materialization as its own page, joins, aggregation/profiling, sampling, near-duplicate detection, chunking, distributed shuffle, and IVF-partition clustering. **Feature Engineering** -- computed columns and materialized views, restructured to lead with the Function-based path and show the SQL form side by side with Python throughout; a single Auto Refresh page instead of duplicating scheduling details on every refresh page; adaptive execution; checkpointing; GPU and Slurm placement for refresh workers; a Training Cache page for the PyTorch data loader's automatic cache benefit. **Security & Governance** -- an Audit Log reference (schema, access, grants), Secrets promoted to an ordinary catalog object with their own SQL DDL and a vending/rotation guide, and privilege-table fixes verified against the authorization source. **Deployment & Maintenance** -- Horizontal Scaling and OpenTelemetry moved into a real Deployment area; Automated Cleanup folded into Intelligent Auto-Maintenance (every other maintenance decision already lived there); RTE Compaction and Advanced Conflict Resolution documented in depth. **Landing page** -- the Enterprise feature comparison table reorganized (several redundant or stale rows removed, several new areas added), and the "why Enterprise" bullets replaced with ones tied to a concrete page (Performance, Scale, Fault tolerance, Multicloud deployment, Simplify operations) instead of vague promises. Plus a full pass addressing lancedb-gatekeeper's review: a real test-safety bug (a quickstart test could silently overwrite and delete a deployment's own `frames` table), a fabricated SQL statement with no backing implementation, an actual dedup-guarantee bug in `take_row_ids`, and dozens of documentation-accuracy fixes verified against source rather than taken on faith -- each either fixed, or left with an explicit note on why it needs a feature or deployment owner's sign-off instead of being guessed at. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_018PXMCbRH6i5w47TsjeEUMT --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
35 lines
1.0 KiB
Plaintext
35 lines
1.0 KiB
Plaintext
---
|
|
title: "Delete"
|
|
sidebarTitle: "Delete"
|
|
description: "DELETE FROM ... WHERE: rows are marked, not erased."
|
|
icon: trash
|
|
keywords: ["delete", "sql"]
|
|
availability:
|
|
embedded: unavailable
|
|
enterprise: available
|
|
---
|
|
|
|
<CodeGroup>
|
|
```sql SQL icon="database"
|
|
DELETE FROM documents WHERE created_at < TIMESTAMP '2025-01-01 00:00:00'
|
|
```
|
|
</CodeGroup>
|
|
|
|
Compare a timestamp column with a typed literal, as above, or with
|
|
`CAST('2025-01-01' AS TIMESTAMP)`. A bare string such as `'2025-01-01'` is
|
|
rejected in a `DELETE` predicate, even though a `SELECT` accepts it.
|
|
|
|
Deletion marks rows rather than erasing them, so the data remains recoverable
|
|
for as long as the version holding it survives
|
|
[retention](/maintenance/cleanup).
|
|
|
|
Commits a new table version, so [versioning](/management/table#versioning) and
|
|
the [write guarantees](/basics/guarantees#writes) apply, including that the
|
|
version advances even when the statement affects zero rows.
|
|
|
|
## What to read next {#next}
|
|
|
|
<Card title="Delete" icon="trash" href="/ingestion/delete">
|
|
The SDK equivalent.
|
|
</Card>
|