{{ message }}
Repository navigation
fix(mysql): set stringifyObjects implicitly - #11574
Merged
Merged
Conversation
Contributor
commit: |
OSA413
approved these changes
Jul 20, 2025
gioboa
approved these changes
Jul 20, 2025
1 of 18 tasks
ThbltLmr
pushed a commit
to ThbltLmr/typeorm
that referenced
this pull request
Dec 2, 2025
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Description of change
Pass
stringifyObjects: trueto themysql2client to avoid any unexpected behavior.It should not really affect the users though, as they should send valid data to TypeORM in most scenarios, but it can be disabled by passing
stringifyObjects: falsein theextraconnection options if needed.Pull-Request Checklist
masterbranchFixes #00000Summary by CodeRabbit