{"action":"closed","issue":{"url":"https://api.github.com/repos/npgsql/npgsql/issues/1187","repository_url":"https://api.github.com/repos/npgsql/npgsql","labels_url":"https://api.github.com/repos/npgsql/npgsql/issues/1187/labels{/name}","comments_url":"https://api.github.com/repos/npgsql/npgsql/issues/1187/comments","events_url":"https://api.github.com/repos/npgsql/npgsql/issues/1187/events","html_url":"https://github.com/npgsql/npgsql/issues/1187","id":163571810,"number":1187,"title":"Please bring back NpgsqlException.ErrorSql","user":{"login":"realityexists","id":856400,"avatar_url":"https://avatars.githubusercontent.com/u/856400?v=3","gravatar_id":"","url":"https://api.github.com/users/realityexists","html_url":"https://github.com/realityexists","followers_url":"https://api.github.com/users/realityexists/followers","following_url":"https://api.github.com/users/realityexists/following{/other_user}","gists_url":"https://api.github.com/users/realityexists/gists{/gist_id}","starred_url":"https://api.github.com/users/realityexists/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/realityexists/subscriptions","organizations_url":"https://api.github.com/users/realityexists/orgs","repos_url":"https://api.github.com/users/realityexists/repos","events_url":"https://api.github.com/users/realityexists/events{/privacy}","received_events_url":"https://api.github.com/users/realityexists/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/npgsql/npgsql/labels/invalid","name":"invalid","color":"fbca04"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-07-03T17:36:47Z","updated_at":"2016-07-03T17:53:40Z","closed_at":"2016-07-03T17:53:40Z","body":"In the upgrad from Npgsql 2 to 3.1 the `NpgsqlException.ErrorSql` property seems to have been lost. This was very useful for logging what SQL caused a problem. Could you please add this back?"}}
{"actor":{"display_login":"roji"}}