Using versions to build records and adjusting the demo to use this

A record is now a collection of versions. A version is a collection
of operations. Data can be overwritten by later versions, still preserving
older versions of data fields.

TODO: This means we actually need an API to scrub data from the history

1 files changed, 2 insertions, 7 deletions

diff --git a/src/record/mod.rs b/src/record/mod.rs
index 0ce20c5..1963ce1 100644
--- a/src/record/mod.rs
+++ b/src/record/mod.rs
@@ -3,8 +3,8 @@
 //! A record is a set of key-value store values with a header
 //!
 
-mod version;
-use self::version::{Version, Operation};
+pub mod version;
+pub use self::version::Version;
 
 use std::collections::BTreeMap;
 use chrono::{DateTime, Local};
@@ -115,11 +115,6 @@ impl Record {
         return first.flatten();
     }
 
-    /// Set a simple key-value pair
-    pub fn set_data(&mut self, key: &str, val: Payload) {
-        // self.body.insert(String::from(key), val);
-    }
-
     /// Add a new tag to this record head. Checks that tags don't already exists
     pub fn add_tag(&mut self, tag: &str) {
         self.header.tags.push(String::from(tag));