Avoid fatal error when the SQLite directory needs to be created #102
Conversation
This file contains 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
konvpalto
added a commit
that referenced
this pull request
Aug 2, 2014
Also check if DB path doesn't point to a directory. By: Nick Farrell GitHub: #102 Signed-off-by: Eygene Ryabinkin <rea@codelabs.ru>
|
Pushed 73e2c95 into "next": it carries slightly modified patch. Thanks! |
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.
I was getting nasty fatal exceptions when I was trying to create a mapping from INBOX on exchange 2010 to gmail. Finally I realised the problem was not with the name of the exchange IMAP folder, but simply because the SQLite database file was being created in a directory which didn't yet exist!