-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing support for VALUES list in SELECT statements #1300
Comments
This should get implemented in Please create a new issue over https://github.com/spring-projects/spring-framework/issues and leave a link to it here. Thanks. |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
I created an issue in spring framework. |
Thanks |
Currently spring-data-jdbc does not support
SELECT
statements that use theVALUES
keyword::ids
is not properly expanded (it needs to put every list entry into()
) and thus generates wrong SQL.I know this would be complex to support for complex objects types as
IN
-statements works with tuples in some databases but the simple, one-valued variant should be pretty straightforward.At least PostgreSQL generates different plans for a simple
IN
vsIN VALUES
clause, especially when the input list is big (>100) which perform quite differently (10-30% worse for us).Using a
VALUES
list is also interesting when using CTE (WITH
) to populate a temporary table with user provided input, this is not achievable with anIN
statement.Disclaimer: I haven't checked if
VALUES
expansion works in customINSERTS
The text was updated successfully, but these errors were encountered: