Skip to content

Conversation

@hgwr
Copy link
Contributor

@hgwr hgwr commented Jan 23, 2026

Fix binding for EclipseLink when a derived query collapses to ... IS NULL AND ... = ?2 and the provider reports only position 2. We now bind positional parameters based on the reported positions (falling back to the previous size heuristic when no positional metadata is available).

This prevents Query argument 2 not found seen in #4167. Reproducer and logs: #4167 (comment).

Tests: ./mvnw -pl spring-data-jpa -Dtest=NamedOrIndexedQueryParameterSetterUnitTests test (local eclipselink-test fork still fails due to the existing EclipseLink javaagent ASM error).

@hgwr hgwr force-pushed the fix-el-positional-underreport branch from cfad1d4 to 238d679 Compare January 23, 2026 04:42
@mp911de mp911de self-assigned this Jan 26, 2026
@mp911de mp911de added type: bug A general bug status: declined A suggestion or change that we don't feel we should currently apply type: regression A regression from a previous release and removed status: waiting-for-triage An issue we've not yet triaged type: bug A general bug labels Jan 26, 2026
@mp911de
Copy link
Member

mp911de commented Jan 29, 2026

The problem is that the parameter binding index is being incremented leading to gaps in numbering and that is the actual problem to be fixed. Closing in favor of 747a3ee.

@mp911de mp911de closed this Jan 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: declined A suggestion or change that we don't feel we should currently apply type: regression A regression from a previous release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants