[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: KDE/kdepim/kpilot/kpilot
From:       Reinhold Kainhofer <reinhold () kainhofer ! com>
Date:       2005-05-14 8:58:53
Message-ID: 200505141059.00959.reinhold () kainhofer ! com
[Download RAW message or body]


Am Samstag, 14. Mai 2005 04:03 schrieb Jason vanRijn Kasper:
> SVN commit 413429 by vanrijn:
>
> - big changes...
> - before this, the backup strategy was to only do a full file copy if
>   fullSync was used.  Also, if fullSync was done, the database wasn't
>   marked as non-dirty, so databases were continually re-backed-up even
>   though they had not changed.
> - now the strategy for backups are as follows....  unless fullSync is
>   specified, check to see if the database has any modified records in it.
>   if it does not (and we're not doing a fullSync), then we don't need to do
>   anything further.  if it does have changes (or we're asked to do a
>   fullSync), then do a full database copy from Pilot to filesystem (as
>   opposed to a record-by-record database-rebuild-and-save).
>   finally, if we have backed up a database, then we reset the sync flags so
>   we don't have to do it again unless it legitimately changes.

Doesn't this interfere with the conduits? In particular, the same database 
(e.g. ToDoDB) is synced with the conduit, which resets the sync flags. Now 
the backup won't touch it any more and the ToDoDB.pdb on disk (in the backup) 
will be constantly out of date...

Reinhold


-- 
------------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: reinhold@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer / KPilot maintainer

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]