{"action":"created","issue":{"url":"https://api.github.com/repos/larshp/abapGit/issues/250","repository_url":"https://api.github.com/repos/larshp/abapGit","labels_url":"https://api.github.com/repos/larshp/abapGit/issues/250/labels{/name}","comments_url":"https://api.github.com/repos/larshp/abapGit/issues/250/comments","events_url":"https://api.github.com/repos/larshp/abapGit/issues/250/events","html_url":"https://github.com/larshp/abapGit/issues/250","id":159223486,"number":250,"title":"Refactoring: centralize db commits, move it to models","user":{"login":"sbcgua","id":15635498,"avatar_url":"https://avatars2.githubusercontent.com/u/15635498?v=3","gravatar_id":"","url":"https://api.github.com/users/sbcgua","html_url":"https://github.com/sbcgua","followers_url":"https://api.github.com/users/sbcgua/followers","following_url":"https://api.github.com/users/sbcgua/following{/other_user}","gists_url":"https://api.github.com/users/sbcgua/gists{/gist_id}","starred_url":"https://api.github.com/users/sbcgua/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sbcgua/subscriptions","organizations_url":"https://api.github.com/users/sbcgua/orgs","repos_url":"https://api.github.com/users/sbcgua/repos","events_url":"https://api.github.com/users/sbcgua/events{/privacy}","received_events_url":"https://api.github.com/users/sbcgua/received_events","type":"User","site_admin":false},"labels":[{"id":524129630,"url":"https://api.github.com/repos/larshp/abapGit/labels/refactoring","name":"refactoring","color":"0e8a16","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-06-08T17:14:45Z","updated_at":"2017-06-17T20:53:20Z","closed_at":null,"body":"Follows #219 \n\n> @mrsimpson Commit after each DB-Interaction... Personally, I had thought of coding the COMMIT WORKs ins the Data access class.\n> \n> @sbcgua pushing commits to model is not that bad idea here - all db updates seems atomic: repo synced - update and commit, create package - commit, etc ...\n> \n> @larshp good arguments, lets do it, push it down :smile: it should be possible to limit COMMIT WORK to some of the methods in LCL_PERSISTENCE_DB. Guess ROLLBACK WORK will not be needed anywhere.\n"},"comment":{"url":"https://api.github.com/repos/larshp/abapGit/issues/comments/309239560","html_url":"https://github.com/larshp/abapGit/issues/250#issuecomment-309239560","issue_url":"https://api.github.com/repos/larshp/abapGit/issues/250","id":309239560,"user":{"login":"bigld","id":4643389,"avatar_url":"https://avatars3.githubusercontent.com/u/4643389?v=3","gravatar_id":"","url":"https://api.github.com/users/bigld","html_url":"https://github.com/bigld","followers_url":"https://api.github.com/users/bigld/followers","following_url":"https://api.github.com/users/bigld/following{/other_user}","gists_url":"https://api.github.com/users/bigld/gists{/gist_id}","starred_url":"https://api.github.com/users/bigld/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bigld/subscriptions","organizations_url":"https://api.github.com/users/bigld/orgs","repos_url":"https://api.github.com/users/bigld/repos","events_url":"https://api.github.com/users/bigld/events{/privacy}","received_events_url":"https://api.github.com/users/bigld/received_events","type":"User","site_admin":false},"created_at":"2017-06-17T20:53:20Z","updated_at":"2017-06-17T20:53:20Z","body":"how should we deal with implicit commits? HTTP communication will do this!"}}
{"actor":{"display_login":"bigld"}}