complex synchronize problem

[nano8443]

I would like to explain a usecase I have with two colleagues using the same database file, that is stored in an subversion repo.
The database file in subversion is using the subversion feature "write-lock". That means the file is read only on disk unless you request the svn lock. Keepassxc setting "automatic save on change" is enabled.
Usually I have open the database the whole day on my desk and do only "read stuff" to get passphrases out of the database. Then it comes to an point in time, where I have to create a new entry. So I create the entry in keepassxc, fill in a new passphrase and try to save the database.
That is'nt possible because it is read only. So I do a "svn lock". Here, subversion is reporting "you cannot get the lock, because you have to update your local copy first". So I do a "svn update". Now the keepassxc database file is written with the new entry on disk.
But! Keepassxc does not synchronize the changes, coming with "svn update" to the database file in this situation. If I "svn commit" this file, changes made by a colleague bevore are overwritten.
In contrast the synchronization took place if the database is just opened in keepassxc without a pending "write attempt" and you do an "svn update" in background.
In keepass2, there is an additional dialog in this situation asking to merge or overwrite the file.
Thanks for reading! :-)

[droidmonkey]

Make sure you are running our latest version, 2.7.10, we explicitly improved this scenario

[nano8443]

Ahhh! I´m using 2.8.0-snapshot on Windows and 2.7.10 on Linux so far.
After changing to keepasssxc 2.7.10 on Windows I can confirm, that you are right and database merge works perfectly in this situation.
Thank you!