From 05336116a47af2ca0403bedce878264c7e4ba320 Mon Sep 17 00:00:00 2001
From: Joey Hess <joey@kitenet.net>
Date: Thu, 13 Mar 2014 19:37:41 -0400
Subject: [PATCH] implemntation plan

---
 doc/design/caching_database.mdwn | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/design/caching_database.mdwn b/doc/design/caching_database.mdwn
index e789244f7f..5223fa9337 100644
--- a/doc/design/caching_database.mdwn
+++ b/doc/design/caching_database.mdwn
@@ -21,6 +21,15 @@ generated and updated by looking at the git repository.
 Store in the database the Ref of the branch that was used to construct it.
 (Update in same transaction as cached data.)
 
+## implementation plan
+
+1. Implement for metadata, on a branch, with sqlite.
+2. Make sure that builds on all platforms.
+3. Add associated file mappings support. This is needed to fully
+   use the caching database to construct views.
+4. Store incremental fsck info in db.
+5. Replace .map files with 3. for direct mode.
+
 ## case study: persistent with sqllite
 
 Here's a non-normalized database schema in persistent's syntax.