DuckDBService

DuckDBService manages data storage and querying using DuckDB as the database. QuestionRouter uses DuckDBService to execute and fetch results from SQL queries as part of structured query execution. QuestionRouter uses DuckDBService to execute and fetch results from SQL queries as part of structured query execution. DuckDBService and PgDataService are separate services managing database queries for different systems. ExportService uses DuckDBService to export query results in various formats. PgDataService and DuckDBService manage SQL database queries for PostgreSQL and DuckDB respectively. DuckDBService uses the DuckDB file as physical storage for per-project data (e.g., project_4.duckdb). PgDataService replaces DuckDBService as the data service backend for written extraction data. Backend currently uses DuckDBService for managing extracted data storage and querying. PgDataService replaces DuckDBService within the Backend as the data storage service. DuckDBService manages Project 14 DuckDB file for extracted data operations. DuckDBService provides database connections and query execution needed by QueryDataSkill. PgDataService is an alternative service managing PostgreSQL connections, complementing DuckDBService for DuckDB database management. QuestionRouter uses the DuckDB Service for executing SQL queries and accessing data. DuckDB Service is defined in backend/app/services/duckdb_service.py. The execute_query method is part of the DuckDB Service. Project Storage is used by the DuckDB Service to store project-specific DuckDB files.