[chandler-users] collection size after upgrade

[Grant Baillie]

On 14 Feb, 2008, at 09:34, Jeffrey Harris wrote:

> Hi Rick,
>
>> I'll be interested in hearing your reaction to all this because I  
>> suspect that this wasn't supposed to happen. Reading between the  
>> lines, you might guess that my experience with upgrades (of ANY  
>> software) has often included negative consequences, for which I  
>> prepare.
>
> I experienced the same thing yesterday, and filed bug 11842 for  
> this. Automatic backups aren't much use if they get deleted on  
> upgrade!  I'm glad you didn't actually lose any data.

I actually just noticed some worse behaviours (IMHO) about automatic  
backup.chex creation today (for which I'll file a bug, or maybe just  
tack this onto yours):

- If you press cancel during the export process, your old backup.chex  
is erased.
- If you force quit Chandler during the export process, you get a  
partial (i.e. unreloadable) backup.chex.

Both of these can be mitigated by having the app write data to a  
temporary file first, before moving the final, completed file over to  
backup.chex. IIRC, in practice, this can be a little tricky,  
especially on Windows.
--Grant