Actually it might a time_t abi problem.
the sqlite3 integers are 64-bit, and in the file creation function it produces a value such as 1712840079336130048 with length 61 bits which fits.
however the mtime attribute update in the same tmpfs example produces a 91 bit timestamp such as 1442900879053675920712840079
Actually it might a time_t abi problem.
the sqlite3 integers are 64-bit, and in the file creation function it produces a value such as
1712840079336130048 with length 61 bits which fits.
however the mtime attribute update in the same tmpfs example produces a 91 bit timestamp such as 5920712840079
144290087905367