Add support for named in-memory databases using the ?mode=memory connection query param #330
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.
In addition to
:memory:SQLite also provides amode=memoryconnection query param to instruct SQLite to use a named in-memory database. This is especially useful in combination withcache=sharedsince it allows the use of distinct in-memory databases within the same process (see SQLite docs.In my case, I had issues with the in-memory database in my integration tests when using transactions as described in #229). Using
cache=sharedsolved those issues, but introduced another: all tests now shared a common database and weren't isolated anymore. Withfile:memdb${randomId()}?mode=memory&cache=sharedI can create a new in-memory database for each test with a shared cache.