-
Notifications
You must be signed in to change notification settings - Fork 356
DATAJDBC-356 - Support for reading large resultsets #903
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
DATAJDBC-356 - Support for reading large resultsets #903
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent PR.
I have just the single request to change the behaviour in the presence of a ResultSetExtractor
.
As another side note: The "Closes" and "Original pull request" should reference the github issue number and the number of this PR.
But I'm happy to add these when merging
...ata-jdbc/src/main/java/org/springframework/data/jdbc/repository/query/AbstractJdbcQuery.java
Outdated
Show resolved
Hide resolved
...ata-jdbc/src/main/java/org/springframework/data/jdbc/repository/query/AbstractJdbcQuery.java
Show resolved
Hide resolved
182faef
to
b24cb44
Compare
@schauder I finally got to finish this up! |
Use queryForStream for streamed query results. ResultSetExtractor is ignored because it cannot be used together with streams. Closes spring-projects#356
Specifying a custom result set extractor doesn't make sense when using streams because the result set extractor always considers the entire result. This loads the entire stream into memory anyways.
b24cb44
to
e23842b
Compare
Thanks. |
Support for reading large result sets using the new
queryForStream
methods in Spring Framework 5.3.