niftynei 899d54edd0 bkpr: have onchain_fee records be write-only, don't update in place ... One really rough thing about how we did onchain fees is that the records update every time a new event comes in. The better way to do this is to create new entries for every adjustment, so that reconciliation between printouts isn't a misery. We add a timestamp and `update_count` to these records, so you can roughly order them now (and have a good idea of the last time an event that updated an onchain_fee occurred).		2022-07-28 12:08:18 +09:30
..
Makefile	bkpr: tests for db crud	2022-07-28 12:08:18 +09:30
run-bkpr_db.c	bkpr-tests: first test of plugin bkpr database	2022-07-28 12:08:18 +09:30
run-recorder.c	bkpr: have onchain_fee records be write-only, don't update in place	2022-07-28 12:08:18 +09:30
test_utils.h	bkpr-tests: first test of plugin bkpr database	2022-07-28 12:08:18 +09:30