fix(example): reset persisted benchmark schema - #347
Draft
chrispader wants to merge 1 commit into
Draft
Conversation
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.
The benchmark database file persists across app restarts, but its module-scoped connection state does not. A fresh runtime can therefore reopen the existing
Testtable and fail before the benchmark starts. This extracts Samuel Scheit's fix from #298 by rebuilding the expected schema transactionally before inserting benchmark data. A native regression test starts with an incompatible table and checks that the reset restores every benchmark column.Reproduction
Before this change, the second run can fail because
Testalready exists. After this change, the reset replaces the persisted table before inserting benchmark rows.Closes #345.