fix: sqlite-node initialize error - #1706
Closed
KotoriMinami wants to merge 1 commit into
Closed
Conversation
|
@KotoriMinami is the reason you closed this PR is to replace it in favor of this? #1707 |
Author
Yes, since I'm not very familiar with using the PR feature, and I found that the current submission wasn't thorough enough, I created a new one. |
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
2 participants
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.
If this instance is not closed, it will result in the occupation of the database file.
This leads to calling the
unsafeDestroyEverythingmethod duringsetUpWithSchema.Although the connection of the new instance is closed,
an error
resource busy or lockedstill occurs when executingfs.unlinkSync.This fixes #1705