Hi,
I observe, that the backup time in pdb files in backup folder is only set for the standard DBs such as AddressDB.pdb, but not for arbitral DBs. Instead there the backup time is set to Jan 1 1904 - 07:00 UTC
Is that intended?
-Ulf
On 5/14/24 09:05, Ulf Zibis wrote:
Hi,
I observe, that the backup time in pdb files in backup folder is only set for the standard DBs such as AddressDB.pdb, but not for arbitral DBs. Instead there the backup time is set to Jan 1 1904 - 07:00 UTC
Is that intended?
-Ulf
During a sync or backup the dates on the pdb files are compared against
the dates on the corresponding files on the local (desktop). If the
dates match then there is no sync or backup needed. If they do not then
jpilot will sync the file or back it up and set the local date to the
same as what is on the Palm file.
Judd
Am 14.05.24 um 18:20 schrieb Judd Montgomery:
On 5/14/24 09:05, Ulf Zibis wrote:
Hi,
I observe, that the backup time in pdb files in backup folder is only set for the standard DBs such as AddressDB.pdb, but not for arbitral DBs. Instead there the backup time is set to Jan 1 1904 - 07:00 UTC
Is that intended?
-Ulf
During a sync or backup the dates on the pdb files are compared against
the dates on the corresponding files on the local (desktop). If the
dates match then there is no sync or backup needed. If they do not then
jpilot will sync the file or back it up and set the local date to the
same as what is on the Palm file.
Judd
Hi Judd,
thanks for your response.
I suspect, you have misunderstood. I'm not talking about the file times in the file system. I'm talking about the 3 date fields in every PDB file header. These are "created date" "modified date" and "backup date". The last interesting one doesn't exist in filesystems by the way. It's a Palm file special field to log the date of the last backup from handheld to PC. In case of e.g. AddressDB.pdb it is updated to the valid value, but not in case of other PDB files from other Apps, in my case "PolyNote Items.pdb" or even "Messages Database.pdb".
-Ulf