This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Multiple connections to SQLite DB #1879
Merged
Conversation
This file contains 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
vardan10
force-pushed
the
1866-multiple-connections-to-SQLite-DB
branch
from
a3091d2 to
9e278b6
Compare
Codecov Report
@@ Coverage Diff @@
## release/0.7.0 #1879 +/- ##
==============================================
Coverage 66.62% 66.62%
==============================================
Files 298 298
Lines 5229 5229
Branches 941 941
==============================================
Hits 3484 3484
Misses 1745 1745 |
sameersubudhi
approved these changes
Oct 25, 2023
vardan10
force-pushed
the
1866-multiple-connections-to-SQLite-DB
branch
from
993489b to
d099e69
Compare
sameersubudhi
added a commit
that referenced
this pull request
Oct 27, 2023
sameersubudhi
added a commit
that referenced
this pull request
Oct 27, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What was the problem?
This PR resolves #1866
How was it solved?
How was it tested?
Deployed against testnet and indexed more than 15k blocks without any error.