[owncloud-user] client etag rescan by removing .csync_journal.db

Hi, This is to let you know what we do certain migration situations when the etags on the server are lost or scrambled. I would like to know if anyone is having a similar practice or if client developers see any problem with that (and are aware that we use this as a feature of the system). We

Re: [owncloud-user] client etag rescan by removing .csync_journal.db

On 25/09/14 17:26, Jakub Moscicki wrote: This is to let you know what we do certain migration situations when the etags on the server are lost or scrambled. I would like to know if anyone is having a similar practice or if client developers see any problem with that (and are aware that we

Re: [owncloud-user] client etag rescan by removing .csync_journal.db

I will have to connect quite inexperienced computer users at a distance. So I'm not in favour of rebuilding the client db with all risk of problems. Using ETags is a good invention and I strongly advocate for having them predictable and no need for intervention on the client machines. On Sept.