{"action":"opened","issue":{"url":"https://api.github.com/repos/GISeHealth/qgis-versioning/issues/19","labels_url":"https://api.github.com/repos/GISeHealth/qgis-versioning/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/GISeHealth/qgis-versioning/issues/19/comments","events_url":"https://api.github.com/repos/GISeHealth/qgis-versioning/issues/19/events","html_url":"https://github.com/GISeHealth/qgis-versioning/issues/19","id":115589792,"number":19,"title":"Conflicts - No apparent conflict behaviour","user":{"login":"ymoisan","id":7468595,"avatar_url":"https://avatars.githubusercontent.com/u/7468595?v=3","gravatar_id":"","url":"https://api.github.com/users/ymoisan","html_url":"https://github.com/ymoisan","followers_url":"https://api.github.com/users/ymoisan/followers","following_url":"https://api.github.com/users/ymoisan/following{/other_user}","gists_url":"https://api.github.com/users/ymoisan/gists{/gist_id}","starred_url":"https://api.github.com/users/ymoisan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ymoisan/subscriptions","organizations_url":"https://api.github.com/users/ymoisan/orgs","repos_url":"https://api.github.com/users/ymoisan/repos","events_url":"https://api.github.com/users/ymoisan/events{/privacy}","received_events_url":"https://api.github.com/users/ymoisan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-06T21:05:06Z","updated_at":"2015-11-06T21:05:06Z","closed_at":null,"body":"Case of two spatialite files checked out at same central DB revision.  \r\n\r\nConflicts will be flagged ONLY if BOTH spatialite files were modified for any attribute of conflicting feature.  Why is that a problem ?  Because when the first user commits changes and the second updates, then if the second user did not make changes in attributes the local file will be overriden.  There is no apparent conflict, because first user changed something but not second.  But what if second considers his revision is good ?  The current behaviour is that the plugin will override the local file and just say \"You are up to date\".\r\n\r\nAnother case is that of modifying only the geometry.  In that case updating will result in the first user's geometry change to be duplicated in the second user's local file.  The result will be that the second user will get a \"You are up to date\" message with a local file that does not correspond to the central database (because it has one more record because of the change in geometry).  When the second user tries to commit, he gets \"nothing to commit\" : \r\n![no-mods-2-features](https://cloud.githubusercontent.com/assets/7468595/11008611/b132f408-849f-11e5-969d-2482d9afb28a.png)\r\n\r\nThe two dots show the original location and the location moved and committed by the first user.\r\n\r\nWouldn't we need a more robust way of identifying changes ?\r\n"}}