Add examples to db operators docs

[adityaoberai]

What does this PR do?

Adds more examples + fix title and path of operators docs

Test Plan

• bun i && bun dev
• Visit /docs/products/databases/transactions

Related PRs and Issues

• Add DB operators docs #2538
• Simplify headings #2577

Have you read the Contributing Guidelines on issues?

Yes

Summary by CodeRabbit

• Documentation
  • Reorganized database operators documentation to a new location within the Concepts section.
  • Updated navigation structure and internal documentation links to reflect the new documentation path.

[coderabbitai]

Walkthrough

This change relocates the database operators documentation from the URL path /docs/products/databases/db-operators to /docs/products/databases/operators. The modification involves: deleting the old documentation page and creating a new one at the updated path with comparable content structure; updating hyperlinks in two blog posts to reference the new documentation URL; and reorganizing the navigation menu in the databases layout to replace a "Database operators" item in the Journeys section with an "Operators" item under Concepts, along with updated badge dates.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Verify that all URL references across the codebase have been consistently updated from /docs/products/databases/db-operators to /docs/products/databases/operators
• Confirm the content migration from the old documentation page to the new page is complete and accurate, especially multi-language code examples and operator definitions
• Validate that navigation menu structure changes in the layout file properly reflect the reorganization (Journeys removal and Concepts addition)
• Check for any remaining broken internal links or outdated references to the old documentation path

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'Add examples to db operators docs' is only partially accurate. While examples are added, the PR primarily reorganizes the documentation structure by moving db-operators content to a new 'operators' route and updating all related references.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch db-operators-docs-examples

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining why this PR is needed, why this solution was chosen, and what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}