mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

use new name for new format export dbs

Browse source 
Delete the old export dbs on upgrade.

Testing this an exporting to a directory with both exporttree=yes and
importtree=yes, it refused to let an interrupted export proceed after
upgrade, with "unsafe to overwrite file". An import resolved the
problem.
This commit is contained in:
Joey Hess 2019-11-06 17:13:39 -04:00
parent 09241f17ed
commit 2f94b5419a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 22 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/todo/sqlite_database_improvements.mdwn
View file

@ -115,8 +115,12 @@ remaining todo:
> clone being used to update the export. The clone can only learn
> export state from the log. It's supposed to recover from such
> situations, the next time an export is run, so should be ok.
> But it might result in already exported files being re-uploaded,
> or other unncessary work.
>
> Testing this an exporting to a directory with both exporttree=yes and
> importtree=yes, it refused to let an interrupted export proceed after
> upgrade, with "unsafe to overwrite file". An import resolved the
> problem. Guess the problem is that the content idenfifier did not
> get recorded in the git-annex branch and the db value was lost on upgrade.
>
> * Keys (IKey, SFilePath, SInodeCache)
> Use scanUnlockedFiles to repopulate the Associated table.