{"action":"created","issue":{"url":"https://api.github.com/repos/keepassxreboot/keepassxc/issues/1874","repository_url":"https://api.github.com/repos/keepassxreboot/keepassxc","labels_url":"https://api.github.com/repos/keepassxreboot/keepassxc/issues/1874/labels{/name}","comments_url":"https://api.github.com/repos/keepassxreboot/keepassxc/issues/1874/comments","events_url":"https://api.github.com/repos/keepassxreboot/keepassxc/issues/1874/events","html_url":"https://github.com/keepassxreboot/keepassxc/issues/1874","id":317155422,"node_id":"MDU6SXNzdWUzMTcxNTU0MjI=","number":1874,"title":"Ability to disable explicit delete before overwriting the database file","user":{"login":"bahchis","id":6289401,"node_id":"MDQ6VXNlcjYyODk0MDE=","avatar_url":"https://avatars1.githubusercontent.com/u/6289401?v=4","gravatar_id":"","url":"https://api.github.com/users/bahchis","html_url":"https://github.com/bahchis","followers_url":"https://api.github.com/users/bahchis/followers","following_url":"https://api.github.com/users/bahchis/following{/other_user}","gists_url":"https://api.github.com/users/bahchis/gists{/gist_id}","starred_url":"https://api.github.com/users/bahchis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bahchis/subscriptions","organizations_url":"https://api.github.com/users/bahchis/orgs","repos_url":"https://api.github.com/users/bahchis/repos","events_url":"https://api.github.com/users/bahchis/events{/privacy}","received_events_url":"https://api.github.com/users/bahchis/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"droidmonkey","id":2809491,"node_id":"MDQ6VXNlcjI4MDk0OTE=","avatar_url":"https://avatars2.githubusercontent.com/u/2809491?v=4","gravatar_id":"","url":"https://api.github.com/users/droidmonkey","html_url":"https://github.com/droidmonkey","followers_url":"https://api.github.com/users/droidmonkey/followers","following_url":"https://api.github.com/users/droidmonkey/following{/other_user}","gists_url":"https://api.github.com/users/droidmonkey/gists{/gist_id}","starred_url":"https://api.github.com/users/droidmonkey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/droidmonkey/subscriptions","organizations_url":"https://api.github.com/users/droidmonkey/orgs","repos_url":"https://api.github.com/users/droidmonkey/repos","events_url":"https://api.github.com/users/droidmonkey/events{/privacy}","received_events_url":"https://api.github.com/users/droidmonkey/received_events","type":"User","site_admin":false},"assignees":[{"login":"droidmonkey","id":2809491,"node_id":"MDQ6VXNlcjI4MDk0OTE=","avatar_url":"https://avatars2.githubusercontent.com/u/2809491?v=4","gravatar_id":"","url":"https://api.github.com/users/droidmonkey","html_url":"https://github.com/droidmonkey","followers_url":"https://api.github.com/users/droidmonkey/followers","following_url":"https://api.github.com/users/droidmonkey/following{/other_user}","gists_url":"https://api.github.com/users/droidmonkey/gists{/gist_id}","starred_url":"https://api.github.com/users/droidmonkey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/droidmonkey/subscriptions","organizations_url":"https://api.github.com/users/droidmonkey/orgs","repos_url":"https://api.github.com/users/droidmonkey/repos","events_url":"https://api.github.com/users/droidmonkey/events{/privacy}","received_events_url":"https://api.github.com/users/droidmonkey/received_events","type":"User","site_admin":false}],"milestone":null,"comments":12,"created_at":"2018-04-24T10:01:18Z","updated_at":"2018-10-30T18:51:15Z","closed_at":null,"author_association":"NONE","body":"When syncing to Google Drive, the regular drive behavior is to create a new version of the file if a file with the same name exists.\r\n\r\nI was not able to achieve the same behavior using safe deletes and without them. From what I noticed, KeePassXC explicitly deletes the database file before moving the newly saved version, resulting in the old file in the trash instead of having another version of the file.\r\n\r\nAn option to disable the delete could also help use other storage cloud providers (e.g. Dropbox) in a more native way regarding the file history.\r\n\r\n## Expected Behavior\r\nWhen the database is saved in a synced folder, a new file version created.\r\n\r\n## Current Behavior\r\nWhen the database is saved in a synced folder, an entirely new file is created and the old is moved to trash.\r\n\r\n## Possible Solution\r\nWhen moving the temporary database file, have an option to disable explicit delete of the database file and let the filesystem/sync process handle it.\r\n\r\n## Context\r\n1. A potential danger of losing the database if something goes wrong during mid-sync and the trash is emptied.\r\n2. The official Google drive sync client sometimes see files as \"filename - copy 1\"  instead of syncing the original file. Makes it difficult to keep track of the up to date file.\r\n3. Hard to work in teams.\r\n\r\nOperating system: Ubuntu 16.04\r\nCPU architecture: x64\r\nKernel: 4.13.0-38-generic\r\n\r\nEnabled extensions:\r\n- Chrome\r\n"},"comment":{"url":"https://api.github.com/repos/keepassxreboot/keepassxc/issues/comments/434425430","html_url":"https://github.com/keepassxreboot/keepassxc/issues/1874#issuecomment-434425430","issue_url":"https://api.github.com/repos/keepassxreboot/keepassxc/issues/1874","id":434425430,"node_id":"MDEyOklzc3VlQ29tbWVudDQzNDQyNTQzMA==","user":{"login":"4javier","id":459381,"node_id":"MDQ6VXNlcjQ1OTM4MQ==","avatar_url":"https://avatars1.githubusercontent.com/u/459381?v=4","gravatar_id":"","url":"https://api.github.com/users/4javier","html_url":"https://github.com/4javier","followers_url":"https://api.github.com/users/4javier/followers","following_url":"https://api.github.com/users/4javier/following{/other_user}","gists_url":"https://api.github.com/users/4javier/gists{/gist_id}","starred_url":"https://api.github.com/users/4javier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/4javier/subscriptions","organizations_url":"https://api.github.com/users/4javier/orgs","repos_url":"https://api.github.com/users/4javier/repos","events_url":"https://api.github.com/users/4javier/events{/privacy}","received_events_url":"https://api.github.com/users/4javier/received_events","type":"User","site_admin":false},"created_at":"2018-10-30T18:51:15Z","updated_at":"2018-10-30T18:51:15Z","author_association":"NONE","body":"I second this one because of a different problem:\r\nRemoving the old file on gdrive and replacing it with a new one assign a new id to the file. While this is not a problem on pc sincyng by gvfs (gnome-online-accounts) given that it reference the file by name, it becomes problematic for keepass client on android like KeepassDX, that uses AOSP filemanager's content-provider to access data on cloud, that in turn return the gdrive's file ID instead of its name.\r\n"}}
{"actor":{"display_login":"4javier"}}