Currently the timestamps are dependent on the regional settings of the user executing ftrove.
The identical nsrl.db appears, for example, with filectime "2024-02-12 11:25:11.280858018 -0400 AST" (time zone Bermuda) or "2024-02-12 16:25:11.280858018 +0100 CET" (time zone Berlin) - at least in an export (did not look into the DB directly).
For a correct numerical evaluation, all timestamps in all sessions should have a uniform basis.
If necessary, a time zone option can be introduced to give the user a choice (perhaps including the value "auto" or "local" to restore the current behavior).
Currently the timestamps are dependent on the regional settings of the user executing ftrove.
The identical
nsrl.db
appears, for example, withfilectime
"2024-02-12 11:25:11.280858018 -0400 AST" (time zone Bermuda) or "2024-02-12 16:25:11.280858018 +0100 CET" (time zone Berlin) - at least in an export (did not look into the DB directly).For a correct numerical evaluation, all timestamps in all sessions should have a uniform basis.
If necessary, a time zone option can be introduced to give the user a choice (perhaps including the value "auto" or "local" to restore the current behavior).