diff options
author | Guilhem Moulin <guilhem@fripost.org> | 2019-05-22 21:36:21 +0200 |
---|---|---|
committer | Guilhem Moulin <guilhem@fripost.org> | 2019-05-27 00:07:30 +0200 |
commit | b86a1141f7e71cb9244ba4c5609b554417b506bb (patch) | |
tree | 58e927addd82931d65e668358cae3dfbe103ccb3 /interimap@.service | |
parent | 06e459f3ccfb407d7587c470c37328df386b6ff6 (diff) |
interimap: fix handling of mod-sequence values greater or equal than 2 << 63.
SQLite processes every INTEGER values as a 8-byte signed integer, so we
need to manually do the conversion from/to uint64_t client-side if we
don't want to overflow or receive floats.
https://www.sqlite.org/datatype3.html#storage_classes_and_datatypes
http://jakegoulding.com/blog/2011/02/06/sqlite-64-bit-integers/
We could also do the same trick for local/remote UIDs, UIDVALITY and
UIDNEXT values to slim the database down at the expense of pre/post-
processing. (Values of SQLite's INTEGER class are 1, 2, 3, 4, 6, or 8
bytes signed integers depending on the manitudes, so we could save some
space for values ≥2³¹.) But that seems a little overkill.
Diffstat (limited to 'interimap@.service')
0 files changed, 0 insertions, 0 deletions