diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-12-10 14:51:04 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-12-10 14:51:04 -0400 |
| commit | a373d36d1b1da3a5b7c7e6d681d39f18e787b40f (patch) | |
| tree | 90379701e02a3988ad2ebb0bbda45edcbc02a205 /doc | |
| parent | dd4d3a4c327948a24bf0e2c7cf82ed66999437aa (diff) | |
check InodeCache in inAnnex et al
This avoids querying the database when the content file doen't exist
(or otherwise fails the provided check). However, it does add overhead of
querying the database, and will certianly impact performance.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/todo/smudge.mdwn | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/todo/smudge.mdwn b/doc/todo/smudge.mdwn index c203c9566..56a79e4d1 100644 --- a/doc/todo/smudge.mdwn +++ b/doc/todo/smudge.mdwn @@ -325,14 +325,11 @@ files to be unlocked, while the indirect upgrades don't touch the files. #### implementation todo list -* inAnnex check should fail in the case where an annexed object is unlocked - and has had its content changed. Could use an InodeCache for - such objects. This parallels how inAnnex checks work for direct mode. * Reconcile staged changes into the associated files database, whenever the database is queried. -* See if the cases where the associated files database is not used can be - optimised. Eg, if the associated files database doesn't exist at all, - we know smudge/clean are not used, so queries for associated files don't +* See if the cases where the Keys database is not used can be + optimised. Eg, if the Keys database doesn't exist at all, + we know smudge/clean are not used, so queries don't need to open the database or do reconciliation, but can simply return none. Also, no need for Backend.lookupFile to catKeyFile in this case (when not in direct mode). |