@structured_data/sql_repair
engine-specific optimization is the capability threshold between Sonnet and Opus
My JOIN query returns duplicate rows and I can't identify why
locate@structured_data/sql_repair
Root cause is many-to-many JOIN without DISTINCT. Sonnet 4.6 for common errors. Opus 4.8 for window functions and engine-specific behavior.
standard SQL errors, high volume, cost-sensitive
claude/sonnet-4.6complex window functions, performance optimization, engine-specific
claude/opus-4.8engine-specific constraint satisfaction required
openai/gpt-5.5| ID | Relation | Actor | Result | Output |
|---|---|---|---|---|
| CT-D7-001 | locate@query_layer | claude/opus-4.8 | accepted | distinguishes WHERE vs JOIN vs subquery vs window function; explains engine constraints |
| CT-D7-002 | locate@query_layer | claude/sonnet-4.6 | bounded | strong on common JOIN and WHERE issues; weaker on complex window functions |
| CT-D7-003 | rewrite@equivalent | claude/opus-4.8 | accepted | explains performance tradeoffs between equivalent rewrites and optimizer behavior |
Opus 4.8 leads on GDPval-AA economically valuable knowledge work including structured data tasks
Anthropic launch, May 2026Sonnet 4.6 sufficient for standard SQL errors in developer preference tests
inferred from Sonnet coding preference data