---
id: TST-PFM-DJE-143
title: Database error classification
kind: unit
product_area: platform
module: data-job-engine
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-crm
files:
  - modules/data-jobs/tests/unit/services/operations/database-error-classification.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: In-memory fixtures and restored dependency doubles.
evidence:
  - >-
    services-crm:modules/data-jobs/tests/unit/services/operations/database-error-classification.spec.js
assertion_inventory:
  - the database’s refusals in a data job
  - rejects only the record for a value too large for the index on its column (54000)
  - rejects only the record for a value longer than its column (22001)
  - rejects only the record for a number out of range (22003)
  - rejects only the record for a date out of range (22008)
  - 'still stops the job for a refusal that is nobody’s record, saying the SQLSTATE and no value'
  - 'never repeats a query error’s bound values, even without a SQLSTATE'
  - keeps the message of an error CRM itself wrote
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Database error classification

## Verification Boundary

The suite checks an isolated production calculation, declaration or adapter. The structured assertion inventory records the checks present at the pinned revision.

## What This Suite Proves

The existing checks exercise database error classification. The specification bindings identify the narrower outcomes supported by those assertions.

## What It Does Not Prove

An isolated check does not establish a deployed workflow, database enforcement or complete feature acceptance.

## Real Dependencies and Test Doubles

The production function or declaration is exercised with in-memory inputs and dependency doubles. This boundary does not require a live database.

## Must Not Be Doubled

The production function under examination and its returned decisions remain real; replacing their answers defeats the check.