fix(flightsql): isolate example SQLite databases - #1067
Open
fallintoplace wants to merge 1 commit into
Open
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
1 participant
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.
Fixes #916
Problem
CreateDB always opened the same named in-memory SQLite database with
cache=shared. Independent server instances created in the same process therefore shared tables and data unexpectedly.Change
Generate a unique database name for each CreateDB call while retaining
cache=shared. Connections obtained from the samesql.DBstill share one in-memory database, but separate CreateDB calls are isolated.Coverage
The regression test verifies both sides of the contract:
sql.DBsee the same dataValidation
go test ./arrow/flight/flightsql/example