How to restore a single point from backups? Ho to explore the contents of a backup?

Claudio Fava shared this question 9 days ago
Answered

How can I restore a single point that I have mistakenly deleted?


I don't want to restore the entire archive!


Is it possible to explore the contents of a backup to read, for example, the coordinates of the points? Thanks

Replies (5)

photo
1

Hi Claudio,

the whole point and track database is backed up. It consists of two DB files readable only in Locus. So you can do so in two Locuses on two devices - you can restore the backup in one device, export the one point in GPX file and then import the point to the first (original) Locus Map.

photo
1

If you are savy enough with a file manager, you can do it with one Locus, and careful backup of current waypoint.db (only this one needed in your case), extract the backup waypoint.db from the backup zip to the right place in data subfolder, start Locus, do the export of the point to file system, exit from Locus. Then re-install your manual waypoint.db copy, start Locus and import your point from the exported file.

If you are not afraid of SQL, you can use a SQLite reader and find your point there.

Which brings me to a message to the Locus team: such manual glitches can easily happen, and the recovery is painful, whichever way you chose.

The introduction of a bin is no rocket science - just a flag to hide the "deleted" objects until the bin is explicitly purged.

CHeers

Michael

photo
1

Thanks to both, I solved with a sql reader.


I would ask you another thing: looking at the db I was looking for the references to the attachments of the points, the photos that link to a point, where do I find them in the db? Thanks

photo
1

The info you're looking for is serialized in the "extra_data" column. Unfortunately, the chance you extract the data from there manually limits to zero...

photo
1

Michal, this makes the bin feature even more relevant.

And it can be as trivial as a Locus track and point folder with a reserved name BiN.

A delete would be a simple move to those respective folders. As I said: trivial to implement.

BiNs cannot be deleted, but their content can by the existing features.

photo
1

Hi Michael, I'm afraid we have a lot to do elsewhere in the app/web at the moment and we definitely don't want to develop a bin that completely dismantles the current sync system. And AFAIK the word "trivial" is no the proper one for such an operation :)

photo
1

I agree, Michal, that there are potential perfectionist designs that cause a lot of pain and effort.

My hint leverages existing features to the highest level. BiN would be synched, as other folders. - what's the issue?

photo
1

PS: the whole ting would be a change in the "delete" function:

if (folder == BiN)

then do the delete as today

else do a move of the object to BiN

No changes anywhere else in the code.

What do you call such?

photo
1

Hello Michael,

Syncing deleted items sounds to me like waste of power/bandwidth. Next to it, there have to be UI where you may see already deleted items and be able to restore it. In many places where app grab data from the DB needs to be exception to exclude "deleted" items. There will be also issues with import & overwrite system and later restore of items that now again exists because they were re-imported after deletion ...

Uff, no sorry, I do not think that this feature is really so important.

Menion

photo
Leave a Comment
 
Attach a file