Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/routes/changelog/(entries)/2025-11-04.markdoc
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
---
layout: changelog
title: "Announcing DB operators: Update multiple fields without fetching the entire row"
title: "Announcing new DB operators: Update multiple fields without fetching the entire row"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix capitalization inconsistency in "DB Operators".

Line 3 uses "DB operators" (lowercase 'o') while line 11 uses "DB Operators" (uppercase 'O'). For consistency in user-facing documentation, standardize the capitalization throughout the document.

Apply this diff to standardize with uppercase:

-title: "Announcing new DB operators: Update multiple fields without fetching the entire row"
+title: "Announcing new DB Operators: Update multiple fields without fetching the entire row"

Also applies to: 11-11

🤖 Prompt for AI Agents
In src/routes/changelog/(entries)/2025-11-04.markdoc around lines 3 and 11, the
phrase "DB operators" is capitalized inconsistently; change both occurrences to
"DB Operators" (uppercase O) so the user-facing document uses the same
capitalization everywhere; update line 3 and line 11 to "DB Operators" ensuring
exact match and preserve surrounding punctuation and spacing.

date: 2025-11-04
cover: /images/blog/announcing-db-operators/cover.png
---
Updating just one field in a row, like incrementing a counter or adding a tag, used to require reading and rewriting the entire document. This added latency, wasted bandwidth, and created risks of lost updates under high concurrency.

**What’s new:**

- Introduced DB Operators v1, enabling inline, atomic field-level updates.
- Introduced new DB Operators, enabling inline, atomic field-level updates.
- Support for numeric, array, string, and date operations.
- Perform multiple field updates in a single atomic call.
- Type-safe SDK methods for clarity and safety.
Expand Down