Fix for 'database does not exist' error #7
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.
If you are using a MySQL database, your app will throw you a 'database does not exist' error after you leave it idle for a few hours. Apparently, MySQL times-out the database connection if it doesn't receive a command for a while (mine turned out to be 8 hours).
Rails doesn't have this problem because it auto-verifies the database connection before it runs the controllers, and re-connects if it needs to. I'm adding this exact same behaviour to the library.
TLDR: You need to call 'ActiveRecord::Base.verify_active_connections!'