-
Notifications
You must be signed in to change notification settings - Fork 356
Support for reading large resultsets [DATAJDBC-356] #578
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
Comments
Marcos Vinicius da Silva commented I stared working on a solution for this issue. I did not started mybatis support yet and will start working on tests and better documentation / examples, but would like to discuss the solution API and implementation wise. For this case, I created some support classes to return an SqlRowSet backed by a connected ResultSet and it's DataSource. I did it this way so I can keep track of all resources and close them when appropriated. I would much appraciate some review on this work in progress, as it is my first Spring contribution. Commit link: detinho@913e8c5 |
Marcos Vinicius da Silva commented I opened a pull request so it's easier to track changes and get feedback. |
Jens Schauder commented The problem with directly using the a But if you could build a solution based on |
I opened a new pull request for this issue. See #903. |
alpet opened DATAJDBC-356 and commented
Enable support for reading large resultsets (milions of rows). Two suggestions:
Without this methods as findAll or findAllByProperty will benefit from having such functionality
No further details from DATAJDBC-356
The text was updated successfully, but these errors were encountered: