Fix error when reading first page from WAL commit in SQLite3 #15
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.
This PR fixes an issue where a
InvalidPageTypewould be thrown when attempting to read data from page 1 of a WAL commit, e.g.Error while executing 'notifications.wpndatabase': Unknown page type: 83.This issue was discussed while working on #9, see: #9 (comment).
Back then I was not able to create a database with data on page 1, and page 1 being in WAL. I have found that the Windows notifications database on both my VM's does this, which allowed me to work on a fix. It is fixed by just moving the head past the header. This fix works on the notifications database.
I have not yet been able to achieve this in Python's SQLite3 library, so there is no new test data.
Required for: fox-it/dissect.target#1454