{"action":"created","issue":{"url":"https://api.github.com/repos/upper/db/issues/226","repository_url":"https://api.github.com/repos/upper/db","labels_url":"https://api.github.com/repos/upper/db/issues/226/labels{/name}","comments_url":"https://api.github.com/repos/upper/db/issues/226/comments","events_url":"https://api.github.com/repos/upper/db/issues/226/events","html_url":"https://github.com/upper/db/issues/226","id":170958559,"number":226,"title":"invalid driver connection: Re-connect automatically (at least once)","user":{"login":"VojtechVitek","id":139342,"avatar_url":"https://avatars.githubusercontent.com/u/139342?v=3","gravatar_id":"","url":"https://api.github.com/users/VojtechVitek","html_url":"https://github.com/VojtechVitek","followers_url":"https://api.github.com/users/VojtechVitek/followers","following_url":"https://api.github.com/users/VojtechVitek/following{/other_user}","gists_url":"https://api.github.com/users/VojtechVitek/gists{/gist_id}","starred_url":"https://api.github.com/users/VojtechVitek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/VojtechVitek/subscriptions","organizations_url":"https://api.github.com/users/VojtechVitek/orgs","repos_url":"https://api.github.com/users/VojtechVitek/repos","events_url":"https://api.github.com/users/VojtechVitek/events{/privacy}","received_events_url":"https://api.github.com/users/VojtechVitek/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-12T21:02:14Z","updated_at":"2016-08-12T21:05:06Z","closed_at":null,"body":"When DB is restarted, all connections are lost and thus invalid. Currently, upper/db returns `invalid driver connection` error back to the caller. Instead, it should should clean-up the connection pool and try to re-connect to the DB (at least once).\r\n\r\nIdeally, this error would be exposed to the client only on interrupted Transaction, or when upper/db can't reconnect to the DB."},"comment":{"url":"https://api.github.com/repos/upper/db/issues/comments/239559499","html_url":"https://github.com/upper/db/issues/226#issuecomment-239559499","issue_url":"https://api.github.com/repos/upper/db/issues/226","id":239559499,"user":{"login":"pkieltyka","id":18831,"avatar_url":"https://avatars.githubusercontent.com/u/18831?v=3","gravatar_id":"","url":"https://api.github.com/users/pkieltyka","html_url":"https://github.com/pkieltyka","followers_url":"https://api.github.com/users/pkieltyka/followers","following_url":"https://api.github.com/users/pkieltyka/following{/other_user}","gists_url":"https://api.github.com/users/pkieltyka/gists{/gist_id}","starred_url":"https://api.github.com/users/pkieltyka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pkieltyka/subscriptions","organizations_url":"https://api.github.com/users/pkieltyka/orgs","repos_url":"https://api.github.com/users/pkieltyka/repos","events_url":"https://api.github.com/users/pkieltyka/events{/privacy}","received_events_url":"https://api.github.com/users/pkieltyka/received_events","type":"User","site_admin":false},"created_at":"2016-08-12T21:05:06Z","updated_at":"2016-08-12T21:05:06Z","body":"it should be a just-in-time mechanism tho.. so as application code requests a connection to make a query, if the last command failed, it try to reconnect, but if it tried within 5 seconds, then it wouldnt try until 5 seconds from now.. ultimately whatever is the easiest / cleanest way and not having to poll in a goroutine and being okay with some errors during the time a connection couldnt be found.. but the goal for it to self recover at some point"}}
{"actor":{"display_login":"pkieltyka"}}