This repository was archived by the owner on Aug 13, 2026. It is now read-only.
fix: reuse MySQL Record Manager DataSource across operations - #6703
Open
baigfaraz wants to merge 1 commit into
Open
fix: reuse MySQL Record Manager DataSource across operations#6703baigfaraz wants to merge 1 commit into
baigfaraz wants to merge 1 commit into
Conversation
Avoid creating and destroying a TypeORM pool on every CRUD call by keeping an instance-level DataSource, releasing QueryRunners after each op, and closing the pool after indexing and document-store deletion. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Avoid creating and destroying a TypeORM pool on every CRUD call by keeping an instance-level DataSource, releasing QueryRunners after each op, and closing the pool after indexing and document-store deletion.