while implementing my Database Blob VFS2 Provider I noticed, that with the
current AbstractFileObject a moveTo() which is delegated to deRename()
cannot be implemented in a atomic way. The renameTo method will call
destFile.delete() and then doRename().
In my JDBC Provider I want to ensure the rename is atomic, this means that
the DELETE and UPDATE JDBC Commands should be in the same commit(). I
could do that with some magic by keeping state between delete and
doRename, but I think it would be easier to simply have the method decide
about the delete itself.
Have you thought about this? I could overwrite the renameTo method, but it
is quite verbose, so the risk is, that I will miss changes if I do so. It
would be better to have a doRename(replace=true) variant?