frappe-syntax-query-builder

Cross-database queries in Frappe are built using frappe.qb, a PyPika-based query builder that constructs safe, parameterized SQL statements. It applies ImportMapper to translate database-specific functions, ensuring your SELECT, JOIN, and aggregation queries execute correctly across MariaDB and PostgreSQL.

The best way to replace raw SQL is migrating to frappe.qb, which enforces DocType-based table references and promotes safe run semantics. This approach prevents SQL injection risks and eliminates syntax drift, allowing you to build production-grade queries for data extraction and reporting.

Yes, frappe.qb fully supports JOINs and subqueries across multiple DocTypes. You can construct complex data extraction and reporting queries by leveraging DocType-based table references to safely interact with data across both MariaDB and PostgreSQL backends.

Yes, frappe.qb supports INSERT, UPDATE, and DELETE operations for Frappe v14 through v16 development. It constructs parameterized queries to safely modify database records, ensuring data integrity checks and cross-database compatibility across MariaDB and PostgreSQL.

You should use frappe.qb instead of raw SQL to avoid brittle, injection-prone code. The query builder enforces DocType-based table references and utilizes parameterized patterns, ensuring portable, safe data extraction across MariaDB and PostgreSQL without risking syntax drift.

The main limitation involves database-specific functions, which frappe.qb handles by utilizing ImportMapper for DB-specific translations. You must adhere to safe run semantics and parameterization to prevent cross-database syntax errors when executing complex queries across MariaDB and PostgreSQL.