Database plugins : Handle the process of releasing connections.
Open
Nobody has claimed this yet.
enhancement
plugins
- Dominant language
- JavaScript
- Stars
- 40.9k
- Forks
- 5.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 202
Description
What is the expected behaviour?
- If a database connection is established directly without using connection pool, release the connection once query is completed.
- When a database connection is from connection pool, release the connection back to pool, once query is completed.
Note: When a new connection is created from the connection pool. Instead of trying to cache the connection, cache the connection pool. The cached connection from the connection pool will be released at the end of query execution. And the connection would become invalid later.
Contributor guide
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 files or tests are named. Start by locating the database plugin paths that establish connections, obtain connections from pools, and complete queries. Done means direct connections are released after queries, pooled connections return to their pool, and the pool rather than an individual connection is cached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100