Skip to content

Fix list expansion parameter name collisions - #2249

Open
alaricd wants to merge 2 commits into
DapperLib:mainfrom
pengdows:fix/issue-1040
Open

alaricd wants to merge 2 commits into
DapperLib:mainfrom
pengdows:fix/issue-1040

Conversation

@alaricd

@alaricd alaricd commented Oct 24, 2026

Copy link
Copy Markdown

Fixes #1040.

When one list parameter name is a prefix of another, expanding the shorter name first causes generated parameter names to be rewritten as part of the longer placeholder. Process list parameters from longest name to shortest and add a fakeDb regression test.

alaricd and others added 2 commits October 24, 2026 07:39
…ctionaries

Generated names (values1 + 1) can equal another list's name (values11), which token
matching cannot distinguish; only expansion order can. Move longest-first ordering into a
shared helper used by both the anonymous-object and DynamicParameters paths, applied only
when a collision is possible so unrelated lists keep their order.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

IN clause is generated with syntax errors when generated variables conflict.

1 participant