Add the ability to specify a path to a database file #5
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
|
Can't comment on the solution but I want this feature. +1 |
|
You can download the new version of the gem, I've submitted your commit (only the first one was necessary). I'm the new maintainer now, here's my fork :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
At present, attempting to point to an sqlite file in a subdirectory or via an absolute path fails spectacularly. This patch provides an update to the README, a couple of tests, and a trivial modification that makes this possible.
I can't work out why the tests I've written actually cause a DB file to be created, while the existing tests don't. AR internals aren't my strong point.