verify-sql-safety

To enforce safe SQL usage in backend search endpoints, you need to verify LIKE escaping for user input, detect N+1 query patterns, and ensure RBAC-compliant inner joins. This process applies to search or list endpoints building dynamic queries.

LIKE escaping for SQL queries is the process of sanitizing user input to prevent unintended wildcard matching or injection. It uses SSOT like-escape utilities, such as likeContains and safeIlike, to ensure consistent and secure search operations across backend services.

Detecting N+1 query patterns in dynamic backend queries involves analyzing service-level query structures to identify inefficient loops and promoting JOIN or batch loading strategies. Proper COUNT(DISTINCT) handling in fan-out joins is also validated to prevent performance bottlenecks.

Yes, this SQL safety verification supports RBAC-compliant inner joins by enforcing them to prevent scope bypass and ensure proper access control. It validates query structures to guarantee that data access is properly restricted according to Role-Based Access Control policies.

To validate safe ilike usage after modifying backend APIs, run a SQL safety verifier to check for consistent use of SSOT like-escape utilities. It catches unsafe LIKE usage and inefficient queries, ensuring secure query practices across your updated search or list endpoints.

A limitation of using like-escape utilities for query safety is the dependency on the project's common utilities like like-escape.ts. You must ensure consistent use of these SSOT utilities across all modules, as bypassing them in dynamic queries can leave search endpoints vulnerable to unsafe SQL patterns.