ArchPilotExecutable architecture guardrails

Search docs

Docs search

Validation rule

Back to Rule Catalog
AP-DQR-002Data / Query Risk

Broad SELECT * usage in query path

Flags broad SELECT * usage in paths where explicit projection is safer.

warningviolationNo auto-fix

How to fix

  1. Replace SELECT * with explicit columns.
  2. Keep sensitive columns out of read models unless required.
  3. Update tests or snapshots that assumed the broad result shape.

What the rule validates

A query returns every column instead of declaring the data it needs.

Why it matters

Broad projection increases data exposure, payload size, and accidental coupling to schema changes.

Common causes

  • Temporary debugging SQL became permanent.
  • Repository methods were copied from exploratory queries.
  • A query grew without revisiting its projection.

Typical violation example

SELECT * FROM account_summary

Typical compliant example

SELECT account_id, balance_cents, status FROM account_summary

Related rules

AP-DQR-001 - Missing tenant filter evidence in multi-tenant SQLAP-DQR-003 - Unbounded query risk without limit/pagination evidenceAP-DQR-004 - Cross-module direct database access bypasses module boundaryAP-DQR-005 - N+1 query evidence in collection loop

Adjacent categories

Data / Query Risk

Related files/config

  • apps/api/src
  • db/sql

Related CLI commands

  • archpilot validate
  • archpilot validate --ci

Related docs

Rule CatalogValidation & Findings
AP-DQR-002 - Broad SELECT * usage in query path | ArchPilot Docs