Scott Lamb 8d9939603e fix repeated deletions within a flush ... When list_oldest_recordings was called twice with no intervening flush, it returned the same rows twice. This led to trying to delete it twice and all following flushes failing with a "no such recording x/y" message. Now, return each row only once, and track how many bytes have been returned. I think dir.rs's logic is still wrong for how many bytes to delete when multiple recordings are flushed at once (it ignores the bytes added by the first when computing the bytes to delete for the second), but this is progress.		2018-02-23 13:49:57 -08:00
..
testdata	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
Cargo.toml	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
coding.rs	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
db.rs	fix repeated deletions within a flush	2018-02-23 13:49:57 -08:00
dir.rs	fix repeated deletions within a flush	2018-02-23 13:49:57 -08:00
lib.rs	knob to reduce db commits (SSD write cycles)	2018-02-22 16:35:34 -08:00
raw.rs	fix repeated deletions within a flush	2018-02-23 13:49:57 -08:00
recording.rs	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
schema.proto	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
schema.rs	initial split of database to a separate crate	2018-02-20 23:15:39 -08:00
schema.sql	extend recording_playback with an open_id	2018-02-22 21:46:41 -08:00
testutil.rs	take FnMut closures by reference	2018-02-23 09:19:42 -08:00