bel-crm-sql-rules

SQL queries for bel-crm must follow strict patterns: use separate read_query and write_query calls, forbid RETURNING and ON CONFLICT clauses, avoid multi-statement queries, and retrieve inserted IDs through a two-step insert-then-read workflow instead of relying on transaction commands.

RETURNING clauses, ON CONFLICT logic, multiple statements in a single call, and transaction commands (BEGIN, COMMIT, ROLLBACK) are unsupported. These limitations require restructuring insert, update, and delete operations into separate compliant read and write operations.

Insert rows using write_query without RETURNING, then execute a separate read_query to fetch the inserted ID by querying the table with appropriate WHERE conditions. This two-step pattern works around the absence of RETURNING support.

No, ON CONFLICT is forbidden in bel-crm. Instead, use a check-then-insert workflow: read_query to detect existing rows, then conditionally execute write_query for insert or update operations based on the result.

Yes, reviewing bel-crm-sql-rules before writing queries prevents errors. The ruleset documents all forbidden patterns (RETURNING, ON CONFLICT, multi-statement, transactions) and prescribes correct CRM-oriented patterns for insert, update, delete, and read operations.