This object is in archive!
Database timestamp updated without change
Answered
When Locus starts, the timestamp of the databases (tracks.db and waypoints.db) is set to the current time.
I know this sounds unimportant, but it messes with filesync tools. I sync my databases on several devices with FolderSync, which uses the timestamp. I take care to only make changes to points and tracks on one device before syncing, and that worked well until some time ago (perhaps version 3.10 or so). Now if I make changes on device A, but merely start Locus on device B after that without making changes, a sync will overwrite my changes on A. I have to manually set the timestamp of the files before syncing.
Does Locus really have to "touch" the databases when nothing changed?
The same question
Hello Ingo,
really hard to say what has changed. Is timestamp changing for both database files (points, tracks)? Also same happen on all devices? > I'm asking because this may be related to database version used in certain Android version.
Hello Ingo,
really hard to say what has changed. Is timestamp changing for both database files (points, tracks)? Also same happen on all devices? > I'm asking because this may be related to database version used in certain Android version.
Don't think that's it. Tried it with 4.2 (S4), 4.4 (Tab Pro) and 5.0 (Note 4) and all show the same behaviour. And at least in April, when I used the S4 and Tab Pro on a longer holiday, that still worked as expected.
I checked it again: When I start Locus, wait for the startup to finish, don't do anything else, and then check the timestamps, they are already updated. So it must be something during the initialization phase.
Don't think that's it. Tried it with 4.2 (S4), 4.4 (Tab Pro) and 5.0 (Note 4) and all show the same behaviour. And at least in April, when I used the S4 and Tab Pro on a longer holiday, that still worked as expected.
I checked it again: When I start Locus, wait for the startup to finish, don't do anything else, and then check the timestamps, they are already updated. So it must be something during the initialization phase.
Oki, understand. I've probably found a place which caused this change. So in next version, database won't be immediately touched during a start. Anyway keep in mind, that what you do is some kind of "hack" and I cannot guarantee that same problem never happen (it probably happen soon or later).
Oki, understand. I've probably found a place which caused this change. So in next version, database won't be immediately touched during a start. Anyway keep in mind, that what you do is some kind of "hack" and I cannot guarantee that same problem never happen (it probably happen soon or later).
Thx, will test it.
Yeah, sure, I know - but I hope this will happen some time, too:
http://help.locusmap.eu/topic/cloud_map_and_data_storage_sync ;)
Then my hack won't be needed anymore. :)
Thx, will test it.
Yeah, sure, I know - but I hope this will happen some time, too:
http://help.locusmap.eu/topic/cloud_map_and_data_storage_sync ;)
Then my hack won't be needed anymore. :)
v3.14.0: Works as expected, no timestamp update at startup. Thx!
v3.14.0: Works as expected, no timestamp update at startup. Thx!
Perfect, you are welcome!
Perfect, you are welcome!
Replies have been locked on this page!