query-compliance

To review SQL queries for injection prevention and performance tuning, enforce parameterized query patterns, least-privilege access, and EXPLAIN analysis. This validates indexing for WHERE and JOIN clauses while flagging anti-patterns like SELECT * to ensure secure database operations.

Query compliance for MongoDB and SQL standardizes how teams write queries, migrations, and schema changes. It prevents insecure database access by requiring parameterized queries, reversible migration workflows, explicit foreign key behaviors, and consistent soft-delete conventions.

Safe database migrations require reversible up and down scripts, staging-tested changes before production, explicit foreign key ON DELETE behaviors, and consistent timestamp usage. This workflow blocks risky production column changes and ensures schema management compliance.

Yes, query compliance rules apply to both MongoDB and SQL environments. The guidelines cover parameterized queries, indexing strategies, pagination, and EXPLAIN ANALYZE performance validation across both database types during code review and performance audits.

The best way to fix N+1 queries and improve database indexing is using proper indexes for WHERE, JOIN, and ORDER BY patterns, applying pagination, and validating performance with EXPLAIN ANALYZE. This eliminates anti-patterns and standardizes efficient query design.