-
Notifications
You must be signed in to change notification settings - Fork 356
Improve performance for batch operations [DATAJDBC-314] #537
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
Labels
has: votes-jira
in: mapping
Mapping and conversion infrastructure
type: enhancement
A general enhancement
Comments
cn-src commented Add |
deleted commented Looks like duplicated by DATAJDBC-328 |
I think supporting batch operations is essential. |
any plan on this? I need it too!! |
Are there any plans for this feature? |
How is this still not a thing? Where do i push a PR for it? |
This was referenced Feb 3, 2022
This was referenced Mar 17, 2022
This was referenced Apr 22, 2022
This got resolved by the various issue and PRs referencing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
has: votes-jira
in: mapping
Mapping and conversion infrastructure
type: enhancement
A general enhancement
Ioannis Daskalakis opened DATAJDBC-314 and commented
Currently, SimpleJdbcRepository batch operations (saveAll, deleteAll) are performed by iterating all instances and performing the operation for each instance separately.
Utilizing batching on the jdbc level (e.g. by utilizing NamedParameterJdbcOperations::batchUpdate) would offer significant performance improvements.
Issue Links:
("is duplicated by")
11 votes, 12 watchers
The text was updated successfully, but these errors were encountered: