Already found parameter binding with same index / parameter name but differing binding type;

[miriyalajanardhan]

After upgrading to spring boot 3.1.3 getting the below error.

Below is the condition which is causing the error. (List regions
)
and ( :regions is null OR lower(c.region) IN (:regions) )

Caused by: java.lang.IllegalArgumentException: Already found parameter binding with same index / parameter name but differing binding type; Already have: ParameterBinding [identifier: regions, origin: MethodInvocationArgument[identifier=regions]], found ParameterBinding [identifier: regions, origin: MethodInvocationArgument[identifier=regions]]; If you bind a parameter multiple times make sure they use the same binding

Same code is working in spring boot 3.1.2

[mp911de]

This has been fixed with #3126. Care to retest against the latest snapshots?

[miriyalajanardhan]

Retried with 3.1.4-SNAPSHOT, still the issue is same.

[mp911de]

Can you please provide a reproducer so we can debug the issue on our side?

[HengCC]

same at #3126 (comment)

[HengCC]

@mp911de
When I downgraded to version 3.0.9, there were no errors,

[gregturn]

@HengCC Could you include a link to a reproducer, staged on github, ideally using https://start.spring.io, H2 (or Testcontainers for PostGreSQL, etc.), and the version of Spring Boot aligned with your issue?

Citing a single comment from another ticket isn't sufficient to hammer out this issue.

It's quite natural that downgrading to an older version that didn't properly support re-used bindings might work, but it reintroduces an older problem we solved.

[HengCC]

@gregturn Thanks for reply, Downgrading can temporarily resolve the issue of the project not running. However,You are correct; downgrading may reintroduce old problems. I have provided a temporary repository for reproducing this issue.

https://github.com/HengCC/jpa-param-index-demo.git

[mp911de]

I'm not able to reproduce the issue anymore, hence closing this ticket.

[HengCC]

@mp911de thanks , I think I've know the reason of this issue . It's still the same demo as above. With the current configuration, the issue no longer occurs

At the very beginning, spring-boot-starter-data-jpa:3.1.4-snapshot still depends on spring-data-jpa:3.1.3.
Perhaps this is due to the IDE's cache or Maven's caching mechanism? Now that I've reverted the configuration, spring-boot-starter-data-jpa:3.1.4-snapshot now depends on spring-data-jpa:3.1.4-snapshot. The issue can no longer be reproduced.

[mp911de]

Spring Boot manages starter versions that do not necessarily map to Spring Data versions. Redeclaring either individual dependency versions, or better, specifying the Spring Data version property (<spring-data-bom.version>2023.0.4-SNAPSHOT</spring-data-bom.version>) is the way to override a dependency.