From d98717156e795936870a0d54fde6d79d51b227c2 Mon Sep 17 00:00:00 2001 From: "claude@clouddev1" Date: Wed, 27 May 2026 10:54:29 +0000 Subject: [PATCH] =?UTF-8?q?fix:=20ADR-0036=20=E2=80=94=20name=20the=20offe?= =?UTF-8?q?nding=20value=20for=20natural-order=20SQL=20INSERTs?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A no-column-list (natural-order / Form B) SQL INSERT that hit a UNIQUE/ CHECK violation degraded to the neutral "that value" because user_value_for_column only resolved the offending value for the explicit- column-list form. Extend user_value_for_column_with_schema to map each VALUES position to the schema's columns in declaration order (ALL columns — advanced-mode Form B auto-fills nothing, so every column has a value), single-row only (multi-row stays ambiguous). Closes the Phase 1 carryover gap so the error names the real value either way. Tests: 1948 passing (+1), 0 failed, 0 skipped, 1 ignored; clippy clean. --- src/runtime.rs | 31 ++++++++++++++-- tests/friendly_enrichment.rs | 71 ++++++++++++++++++++++++++++++++++++ 2 files changed, 99 insertions(+), 3 deletions(-) diff --git a/src/runtime.rs b/src/runtime.rs index 98d8fdd..28c2410 100644 --- a/src/runtime.rs +++ b/src/runtime.rs @@ -1572,9 +1572,11 @@ fn user_value_for_column(command: &Command, column: &str) -> Option