moonfire-nvr/db
Scott Lamb 45f7b30619 allow listing and viewing uncommitted recordings
There may be considerable lag between being fully written and being committed
when using the flush_if_sec feature. Additionally, this is a step toward
listing and viewing recordings before they're fully written. That's a
considerable delay: 60 to 120 seconds for the first recording of a run,
0 to 60 seconds for subsequent recordings.

These recordings aren't yet included in the information returned by
/api/?days=true. They probably should be, but small steps.
2018-03-02 11:38:11 -08:00
..
testdata initial split of database to a separate crate 2018-02-20 23:15:39 -08:00
upgrade refine 1->3 upgrade process 2018-03-01 09:47:56 -08:00
Cargo.toml initial split of database to a separate crate 2018-02-20 23:15:39 -08:00
check.rs update "moonfire-nvr check" for new schema 2018-03-01 17:07:42 -08:00
coding.rs initial split of database to a separate crate 2018-02-20 23:15:39 -08:00
db.rs allow listing and viewing uncommitted recordings 2018-03-02 11:38:11 -08:00
dir.rs update "moonfire-nvr check" for new schema 2018-03-01 17:07:42 -08:00
lib.rs update "moonfire-nvr check" for new schema 2018-03-01 17:07:42 -08:00
raw.rs allow listing and viewing uncommitted recordings 2018-03-02 11:38:11 -08:00
recording.rs allow listing and viewing uncommitted recordings 2018-03-02 11:38:11 -08: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 move open_id from recording_playback to recording 2018-02-28 20:52:43 -08:00
testutil.rs properly account for bytes to add with next flush 2018-03-01 13:50:59 -08:00