Richard van der Hoff b75537beaf Store key validity time in the storage layer ... This is a first step to checking that the key is valid at the required moment. The idea here is that, rather than passing VerifyKey objects in and out of the storage layer, we instead pass FetchKeyResult objects, which simply wrap the VerifyKey and add a valid_until_ts field.		2019-05-23 11:52:22 +01:00
..
12
13	drop tables listed in #1830 (#4992)	2019-04-08 15:37:26 +01:00
14	drop tables listed in #1830 (#4992)	2019-04-08 15:37:26 +01:00
15
16	drop tables listed in #1830 (#4992)	2019-04-08 15:37:26 +01:00
17
18
19
20
21
22
23
24	drop tables listed in #1830 (#4992)	2019-04-08 15:37:26 +01:00
25
26
27
28
29
30	drop tables listed in #1830 (#4992)	2019-04-08 15:37:26 +01:00
31
32	drop tables listed in #1830 (#4992)	2019-04-08 15:37:26 +01:00
33
34	Drop sent_transactions	2018-12-01 23:07:35 -06:00
35
36
37
38
39
40	Add unique indexes to a couple of tables	2018-11-02 10:36:13 +00:00
41
42
43
44
45
46
47
48
49
50
51
52	Merge remote-tracking branch 'origin/develop' into dbkr/e2e_backup_versions_are_numbers	2018-11-09 18:35:02 +00:00
53	Fixup docstrings	2019-04-02 11:20:06 +01:00
54	Store key validity time in the storage layer	2019-05-23 11:52:22 +01:00