It should be great to be able to start a transaction inside a transaction
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.7k
- Forks
- 374
- Avg merge
- 11d 16h
- Merged PRs (30d)
- 1
Description
nothing to do with real postgres transactions
but logically it should be great to be able to imbricate transactions inside the code.
just add something like
transactionSql.begin = ( callback ) => {
return callback( this );
}
this way, when I have a connection or a transaction started by sql.begin i can pass the objet to a method that don't know if it's a transaction
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
No file or test is named. Start by reading the existing sql.begin transaction API and the three-comment discussion, then determine how nested callbacks should behave for a connection or transaction; done means a method can accept either without knowing which it received, with coverage for the requested nesting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100