allow to handle hot-journal (fixes #3135)#3141
Closed
koalo wants to merge 1 commit intopocoproject:develfrom
Closed
allow to handle hot-journal (fixes #3135)#3141koalo wants to merge 1 commit intopocoproject:develfrom
koalo wants to merge 1 commit intopocoproject:develfrom
Conversation
Before, when executing the Poco::Data::SQLite::Utility::fileToMemory method for a SQLite database with an existing hot journal, the method returns successfully, but the resulting in-memory database is corrupted. This is because if a hot journal exists, this can not processed correctly if only read only access to the database is available.
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.
Before, when executing the Poco::Data::SQLite::Utility::fileToMemory method
for a SQLite database with an existing hot journal, the method returns successfully,
but the resulting in-memory database is corrupted.
This is because if a hot journal exists, this can not processed
correctly if only read only access to the database is available.