creating a base sqlite URL with sqlite: instead of sqlite:// #5
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 URL "sqlite://" causes URI::db to turn a relative "dbname" into an absolute path, this may be a bug in URI::db but it is avoided by starting with the URL "sqlite:". "sqlite:foo.db" is unambiguous but "sqlite:///foo.db" is parsed as an absolute path, while "sqlite://localhost/foo.db" is parsed as a relative path. Passing an absolute "dbname" results in the same URL whether you start with "sqlite:" or "sqlite://".