dora-query-pipeline

Manage database query execution, polling, and cancellation across engines.

14|1|Updated May 11, 2025
One-click install
npx skills add https://github.com/remcostoeten/dora --skill dora-query-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dora-query-pipeline
Source: https://github.com/remcostoeten/dora/tree/main/.claude/skills/dora-query-pipeline
Command: npx skills add https://github.com/remcostoeten/dora --skill dora-query-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured framework for managing the complex lifecycle of database queries, ensuring consistent behavior for execution, cancellation, and result handling across different database engines.

Core Features & Use Cases

  • Lifecycle Management: Standardizes how queries are started, polled, cancelled, and reaped to prevent memory leaks and stale data.
  • Engine-Specific Handling: Provides clear rules for managing concurrency and server-side cancellation support across diverse engines like Postgres, SQLite, and DuckDB.
  • Use Case: Use this skill when implementing a new database driver or modifying the query execution path to ensure that cancellation signals are correctly propagated and that result state is properly isolated between tabs.

Quick Start

Consult the query pipeline documentation to verify the statement state machine and engine-specific cancellation requirements before modifying the query execution logic.

Frequently Asked Questions about dora-query-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage database query lifecycle and execution in Rust to prevent memory leaks?

Database query lifecycle management standardizes statement allocation, polling, cancellation, and reaping to prevent memory leaks and stale data. It ensures consistent execution behavior and memory-safe statement reaping across different database engines.

How does database query cancellation work across different engines like Postgres, SQLite, and DuckDB?

Engine-specific cancellation applies clear rules for propagating cancellation signals across Postgres, SQLite, and DuckDB. It manages concurrency and server-side cancellation support to ensure robust state management during query execution.

What's the best way to isolate database query results between concurrent frontend tabs?

Result isolation between frontend tabs requires structured query lifecycle management to separate execution states. Standardizing polling and cancellation ensures each tab receives isolated result sets without cross-contamination from concurrent queries.

Why do I need a state machine for database query execution and statement allocation?

A statement state machine for query execution tracks allocation, polling, and cancellation phases to prevent stale data and memory leaks. It provides robust state management required for memory-safe statement reaping and consistent lifecycle behavior.

Can I use this query lifecycle management framework for backend query services in Tauri applications?

Query lifecycle management applies to backend query services and frontend data providers requiring robust state management and concurrency control. It supports Tauri applications by standardizing execution paths and ensuring proper cancellation signal propagation.