diff options
author | Lars Wirzenius <liw@liw.fi> | 2022-05-03 10:44:26 +0300 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2022-05-03 11:23:38 +0300 |
commit | 3d50e1497dd07929655636cfea0c48ccadd3ab8e (patch) | |
tree | 69770791ebb26ebbce6137ea481e85f19ec35041 /src/db.rs | |
parent | 856d32c448a87245234315462d2190c5a9aab549 (diff) | |
download | obnam2-3d50e1497dd07929655636cfea0c48ccadd3ab8e.tar.gz |
test: add test for storing, retrieving u64::MAX values in JSON
The test passes. We create a FilesystemEntry with a length field
containing u64::MAX, store that into a generation, and read it back.
This works. The entry is serialised into JSON for storing in SQLite,
and this proves we can handle any u64 value in an entry. serde_json
deals with it fine, and we don't need to worry about it.
Sponsored-by: author
Diffstat (limited to 'src/db.rs')
-rw-r--r-- | src/db.rs | 1 |
1 files changed, 0 insertions, 1 deletions
@@ -631,7 +631,6 @@ mod test { } assert_eq!(values, expected); } - #[test] fn round_trips_int_max() { let tmp = tempdir().unwrap(); |