BatchUpdates in SqlServer leads to 'table already exists' on temp tables that were dropped
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
On pathway analyses with multiple Ts, the same analysis sql (with temp tables) is re-run and batch executed, but sql server will concatenate the statements, and then identify duplicated temp tables as 'already exists'.
The proposd fix is to indicate in CancelableJdbcTemplate that supportsBatchUpdate should return false for sql server.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating CancelableJdbcTemplate and inspect how supportsBatchUpdate identifies database types. Reproduce the pathway analysis with multiple Ts and temporary tables on SQL Server if the project provides a relevant entry point or test. Done means SQL Server no longer concatenates these batch statements and the duplicate temporary-table error is avoided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100