OHDSI / OHDSI/DatabaseConnector
ERROR: current transaction is aborted, commands ignored until end of transaction block
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- R
- Stars
- 57
- Forks
- 93
- Avg merge
- 10d 12h
- Merged PRs (30d)
- 1
Description
Whenever I have a sql error using DatabaseConnector's jdbc drivers I need to manually rollback the transaction or disconnect and reconnect to the database.
Can we automatically end the transaction in event of an error so the user does not need to manually end the transaction?
! Error executing SQL:
org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
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 reproducing the SQL error through DatabaseConnector's JDBC drivers and inspect how transaction errors are handled. Done means an SQL error automatically ends or rolls back the transaction so the user does not need to disconnect, reconnect, or manually roll it back.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, r
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100