DSAR-BE-1414: PERSISTENCE_SQL_ERROR

Meaning

A raw SQL query executed by the persistence layer failed.

Probable Causes

• Syntax error in a dynamically constructed query.
• Database connection dropped or timed out mid-query.
• Schema mismatch — a referenced table or column does not exist.
• Constraint violation (unique, foreign key, check) at the database level.

How to Fix

1. Inspect server logs for the full SQL error message and query context.
2. Verify database connectivity and credentials.
3. Ensure migrations have been applied so the schema matches the application's expectations.
4. Check for constraint violations in the input data.

Retryable

Depends on the cause. Connection timeouts are retriable; schema and constraint errors are not.

Response Shape

{
	"ok": false,
	"error": {
		"id": "DSAR-BE-1414",
		"code": "PERSISTENCE_SQL_ERROR",
		"message": "SQL query execution failure",
		"status": 500,
		"trace": {
			"type": "SqlError"
		}
	}
}

Minimal Trigger Example

// Example 1: schema mismatch (column does not exist)
await db.execute(sql`SELECT non_existent_column FROM retention_policies`);
// -> DSAR-BE-1414 (PERSISTENCE_SQL_ERROR)

// Example 2: NOT NULL constraint violation
await db.execute(
	sql`INSERT INTO retention_policies (id, tenant_id, status) VALUES (${id}, NULL, 'active')`
);
// -> DSAR-BE-1414 (PERSISTENCE_SQL_ERROR)