Scott Lamb addeb9d2f6 add a TimerGuard around db locks & ops ... I moved the clocks member from LockedDatabase to Database to make this happen, so the new DatabaseGuard (replacing a direct MutexGuard<LockedDatabase>) can access it before acquiring the lock. I also made the type of clock a type parameter of Database (and so several other things throughout the system). This allowed me to drop the Arc<>, but more importantly it means that the Clocks trait doesn't need to stay object-safe. I plan to take advantage of that shortly.		2018-03-23 13:31:23 -07:00
..
testdata	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
upgrade	make v1->v3 upgrade work with --features=bundled	2018-03-22 09:05:40 -07:00
Cargo.toml	tests and fixes for Writer and Syncer	2018-03-07 04:42:46 -08:00
check.rs	new recording_integrity table	2018-03-09 13:37:30 -08:00
coding.rs	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
db.rs	add a TimerGuard around db locks & ops	2018-03-23 13:31:23 -07:00
dir.rs	tests and fixes for Writer and Syncer	2018-03-07 04:42:46 -08:00
lib.rs	tests and fixes for Writer and Syncer	2018-03-07 04:42:46 -08:00
raw.rs	new recording_integrity table	2018-03-09 13:37:30 -08:00
recording.rs	add a TimerGuard around db locks & ops	2018-03-23 13:31:23 -07:00
schema.proto	more safety around adding/deleting dirs	2018-03-01 12:24:32 -08:00
schema.rs	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
schema.sql	initial schema for user authentication (#26)	2018-03-21 23:57:45 -07:00
testutil.rs	add a TimerGuard around db locks & ops	2018-03-23 13:31:23 -07:00
writer.rs	add a TimerGuard around db locks & ops	2018-03-23 13:31:23 -07:00