moonfire-nvr/db
Scott Lamb 459615a616 include all recordings in days map (fixes #57)
This is a quick fix to a problem that gives a confusing/poor initial
experience, as in this thread:
https://groups.google.com/g/moonfire-nvr-users/c/WB-TIW3bBZI/m/Gqh-L6I9BgAJ

I don't think it's a permanent solution. In particular, when we
implement an event stream (#40), I don't want to have a separate event
for every frame, so having the days map change that often won't work.
The client side will likely manipulate the days map then to include a
special entry for a growing recording, representing "from this time to
now".
2020-07-18 12:13:08 -07:00
..
proto upgrade copyright notices 2020-03-01 22:53:41 -08:00
testdata initial split of database to a separate crate 2018-02-20 23:15:39 -08:00
upgrade use SQLite3 "extra synchronous" pragma 2020-06-08 13:35:45 -07:00
Cargo.toml upgrade deps 2020-04-19 22:19:57 -07:00
auth.rs switch from docopt to structopt 2020-04-17 21:53:37 -07:00
build.rs upgrade deps 2020-04-19 22:19:57 -07:00
check.rs style: use rusqlite's {named_,}params! everywhere 2020-03-19 20:46:25 -07:00
coding.rs upgrade copyright notices 2020-03-01 22:53:41 -08:00
compare.rs upgrade copyright notices 2020-03-01 22:53:41 -08:00
db.rs include all recordings in days map (fixes #57) 2020-07-18 12:13:08 -07:00
dir.rs switch from docopt to structopt 2020-04-17 21:53:37 -07:00
fs.rs upgrade copyright notices 2020-03-01 22:53:41 -08:00
lib.rs upgrade copyright notices 2020-03-01 22:53:41 -08:00
raw.rs style: use rusqlite's {named_,}params! everywhere 2020-03-19 20:46:25 -07:00
recording.rs replace regex use with nom 2020-04-17 21:53:52 -07:00
schema.sql upgrade copyright notices 2020-03-01 22:53:41 -08:00
signal.rs style: use rusqlite's {named_,}params! everywhere 2020-03-19 20:46:25 -07:00
testutil.rs upgrade copyright notices 2020-03-01 22:53:41 -08:00
writer.rs track "assumed" filesystem usage (#89) 2020-07-12 17:15:41 -07:00