This repository has been archived by the owner on May 1, 2023. It is now read-only.
Can only load databases from standard database location #376
Comments
Any updates? |
...and thank you for your patience on this issue! |
Waiting patiently for net release to try it |
Still waiting on this to be released |
@dalewking updated the PR in #392, would you mind verifying that this addresses your issue by pulling the branch ( |
I believe I evaluated that PR when it came out and it worked correctly but I cannot say for sure. Unfortunately, I no longer work for that same company and do not have a good way to test it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue #91 added the ability to specify database files in arbitrary locations not just in the standard location for databases that the context knows about. You can specify your own DatabaseFilesProvider to specify a list of database files, but commit 7a27fc7 broke this support. The problem is this code in SqliteDatabaseDriver.getDatabaseNames():
This code throws away the path information so all you have is the file name and then when you ask the context to open it, it tries to open it from the standard database directory.
The text was updated successfully, but these errors were encountered: