[elephant-cvs] CVS elephant

[ieslick]

Update of /project/elephant/cvsroot/elephant
In directory clnet:/tmp/cvs-serv3903

Modified Files:
	TODO 
Log Message:
Provide checkpoint function

--- /project/elephant/cvsroot/elephant/TODO	2007/02/17 19:28:53	1.53
+++ /project/elephant/cvsroot/elephant/TODO	2007/02/18 10:58:58	1.54
@@ -14,8 +14,6 @@
 TASKS TO GET TO BETA:
 
 BDB Features/Cleanup:
-- Always support locks that timeout?  Tradeoffs?
-- Perform checkpoints (prep for DCM functionality)
 - Derived indices used to fail on re-connect, verify that this is fixed
 
 Lisp Support:
@@ -49,22 +47,21 @@
 Fix any bugs in BETA:
 
 Documentation:
+- License and copyright file headers
 - Add document section about backend interface:
 - Add notes about with/ensure-transaction usage (abort & commit behavior on exit)
 - Add notes about optimize-storage
 - Add notes about deadlock-detect
 - Add notes about checkpoint (null in SQL?)
-- Add notes about new BDB 4.5 *auto-commit* behavior.  Default for entire 
-  store-controller will auto create a transaction if none is active if open 
-  with :auto-commit t or will never auto-commit (regardless of operator flags) 
-  if it is not.  Make sure open-store defaults to auto-commit and there is a 
-  flag to turn it off.
 - More notes about transaction performance
 
 0.6.1 - Features COMPLETED to date
 ----------------------------------
 
+February
+
 February 13-17th, 2007:
+x Allow checkpoint of BDB via db-bdb::checkpoint
 x Fix BDB migration 0.6.0->0.6.1, improve nested transaction/store interactions
 x Legacy conversions issue for SQL (and BDB?) due to package rename (both)
 x Figure out how to compact a specific btree and/or key-range using optimize-storage.
@@ -173,6 +170,9 @@
   (log these in Track)
 
 Features:
+  - Backup function: allow users to specify a backup function to archive the database contents
+    and checkpoint any active functions (how to lock out other threads?)  In BDB this means 
+    running checkpoint and copying the DB files and any active log files.
   - Persistent variables (abstraction that allows compound lisp objects at the cost of
     full serialization after each write that indirects through the API).  Can this be done
     with clean semantics or should we punt it?