I believe there are a few who uses SVN together with KeePass and a very nice feature would be an integration with SVN, for example when synchronizing from/to URL, KeePass could perhaps recognize that this is a SVN repository and be able to commit as well.
I previously worked for a company where the support- and developer organisation was using a KeePass database to keep track of the 2500+ customers environment (databases, servers etc) and the VPN access information for each server. This file was located in a SVN repository. The problem with keeping it there became very obvious when two (or more) employees changed something in an entry, saved the file and tried to commit their changes.
My suggestion is simply that before saving the file, KeePass does an svn update on that file and then merges the changes with the locally changed file and then submits this to the SVN repository together with a comment.
I did a quick test with my own svn repository and chose to open a URL from KeePass. I added an entry to the file and saved and VisualSVN Server responded that there was a conflict.