STET■

flux-pr-1984

sqlparser-rs (Rust) · W1 · GPT-5.1 Codex Mini

graphql-go-tools (Go)sqlparser-rs (Rust)Zod (TypeScript)
W2W1
|
GPT-5.1 Codex Mini
pass_with_warn

Tests passed. 1/1 commands passed. Strength: strong.

100.0% run pass rate
Tier 1
primary testspassedequivalentfail
env PATH=/root/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin cargo test --all-features
gold passagent pass

Partial score: 1/1

Publishable: yesCache: miss

Trajectory

unknown · partial order only

Canonical trajectory missing; showing coarse derived order only.

patch written
Patch captured
#1

Stet captured agent.patch for this trial.

agent.patch
validation
Tests passed
#2
validation
equivalence
Equivalence judgment
#3

equivalent

validation
code review
Code review judgment
#4

fail

validation
decision
Final decision
#5

pass_with_warn

validation

Quality

equivalence
equivalent
86% confidence
code review
fail
3 findings
footprint
low (0.26)
behavioral
0.0%
cost
$2.52 · 6.0M

Equivalence Reasoning

stylistic

The agent patch implements the intended feature: `INTERVAL` now carries optional qualifier metadata, parser logic reads PostgreSQL-style interval qualifiers/precision (including forms like `YEAR TO MONTH` and `HOUR TO SECOND(3)`), and support is gated by a dialect capability enabled for PostgreSQL and Generic only. The structure differs from gold (`IntervalFieldSpec` vs `IntervalFields + precision`) but achieves the same core behavior.

Code Review

correctness: 1/4introduced bug risk: 1/4edge case handling: 1/4maintainability idioms: 2/4

The patch is directionally close but likely does not fully satisfy the intended PostgreSQL interval-option behavior due overly permissive parsing and potentially non-canonical rendering; it is unlikely to be fully correct as-is.

3 findings
Interval qualifier parser is too permissive for PostgreSQL field sets
major

The new parser consumes any temporal unit via `next_token_is_temporal_unit` and `parse_date_time_field`, which likely allows unsupported PostgreSQL data type qualifiers (instead of limiting to YEAR/MONTH/DAY/HOUR/MINUTE/SECOND and valid TO ranges).

src/parser/mod.rs:2977
SECOND qualifier accepts precision-scale form not required by requested behavior
major

For leading `SECOND`, parsing uses `parse_optional_precision_scale`, permitting two numeric arguments, which is broader than the requested PostgreSQL-style subsecond precision support (`SECOND(p)` / `TO SECOND(p)`).

src/parser/mod.rs:2990
Display formatting of interval qualifiers is non-canonical
major

`IntervalFieldSpec` formatting inserts spaces before parentheses (e.g. `YEAR (3)`), which may break expected canonical round-trip output for dialect tests that assert normalized SQL strings.

src/ast/data_type.rs:55
Evidencevalidation (149.7 KB)results (55.9 KB)run_metadata (1.6 KB)agent_patch (14.3 KB)summary (90.8 KB)manifest (475 B)