Feat: Support defaultSafeIntegers option in better-sqlite3 dialect #6320
+94
−1
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
Fixes #6319
This PR adds support for the
defaultSafeIntegersoption in thebetter-sqlite3dialect. Previously, this option was passed in the connection configuration but was not being applied to thebetter-sqlite3database instance.This change allows users to enable
defaultSafeIntegers: trueto receiveBigIntvalues for integers, preventing precision loss for large numbers.Changes
acquireRawConnectioninlib/dialects/better-sqlite3/index.jsto check fordefaultSafeIntegersin connection settings or options and apply it to the database instance usingdb.defaultSafeIntegers().Related Issue
Checklist