[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] resolving name conflicts; implementation
From: |
Thomas Moschny |
Subject: |
Re: [Monotone-devel] resolving name conflicts; implementation |
Date: |
Tue, 19 Aug 2008 16:39:21 +0200 |
User-agent: |
KMail/1.10.0 (Linux/2.6.25-14.fc9.x86_64; KDE/4.1.0; x86_64; ; ) |
Stephen Leake wrote:
> There are two formats for "changes to rosters" stored in the database;
> changesets and roster_deltas.
>
> I'm not clear why we have both.
Well, it's different. Changesets describe the 'original' first class data. For
example, only changesets are transferred in a sync operation between two
databases (and associated file contents, of course), not rosters. Rosters form
strictly local caches that can at any time be regenerated from the changesets.
So, keeping changesets is a form of redundancy (or security, if you wish) in
case something breaks.
As a side note, rosters are stored as roster deltas, and of course, there are
similarities between changesets and roster deltas, so, the idea of changing
our storage format to keep only one of them has already been floating around
for a while. This is not a simple change however, and afaik no one has
implemented something in that direction yet.
- Thomas
signature.asc
Description: This is a digitally signed message part.