added checkPresentExportWithContentIdentifier
Ugh, don't like needing to add this, but I can't see a way around it.
This commit is contained in:
parent
3c652e1499
commit
46d33e804a
5 changed files with 130 additions and 92 deletions
|
@ -10,10 +10,9 @@ this.
|
|||
|
||||
## implementation notes
|
||||
|
||||
* startExport uses checkPresentExport, but when there's a modified file,
|
||||
it's not unexported, so it present, so checkPresentExport succeeds,
|
||||
and so startExport does the wrong thing. Seems to indicate checkPresentExport
|
||||
needs to be replaced too.
|
||||
* Check conflict behavior for both conflicting edits to existing file,
|
||||
and conflicting new files. Note need to check both sequences
|
||||
import,export and export,import.
|
||||
|
||||
* Should the ContentIdentifier db be multiwriter? It would simplify
|
||||
the situation with the long-lived lock of it in adjustExportImport
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue