Right now, it's not generally possible for two people (or one person in two different locations) to use the same KDBX with KPW in edit mode unless they coordinate their actions. For cloud based with Google Drive, there's headRevisionId and modifiedTime on the file, so the app can compare against what it opened and refuse or merge rather than clobber, but that's not done. For local, a checksum could be made at load time at write time to check before writing. But regardless, neither is supported and right now there is no atomic write, concurrent edit lock-out, or anti-clobbering measures in place.
TODO
Right now, it's not generally possible for two people (or one person in two different locations) to use the same KDBX with KPW in edit mode unless they coordinate their actions. For cloud based with Google Drive, there's headRevisionId and modifiedTime on the file, so the app can compare against what it opened and refuse or merge rather than clobber, but that's not done. For local, a checksum could be made at load time at write time to check before writing. But regardless, neither is supported and right now there is no atomic write, concurrent edit lock-out, or anti-clobbering measures in place.
TODO