Hi David. I haven't had a chance to look back at the original code, but
your follow-up expanded comment agrees with how I remember this code
working.
On Aug 7, 2015 4:41 PM, "David Bremner" wrote:
> Daniel Schoepe writes:
>
>
> > On Fri, 05 Jun 2015 19:28 +0200, David Bremner wrote:
> >> +
Hi David. I haven't had a chance to look back at the original code, but
your follow-up expanded comment agrees with how I remember this code
working.
On Aug 7, 2015 4:41 PM, "David Bremner" wrote:
> Daniel Schoepe writes:
>
>
> > On Fri, 05 Jun 2015 19:28 +0200, David Bremner wrote:
> >> +
Daniel Schoepe writes:
> On Fri, 05 Jun 2015 19:28 +0200, David Bremner wrote:
>> +/* Prior to NOTMUCH_FEATURE_LAST_MOD, messages did not
>> + * track modification revisions. Give all messages a
>> + * revision of 1.
>> + */
>> +if (new_features & NOTMUCH
Daniel Schoepe writes:
> On Fri, 05 Jun 2015 19:28 +0200, David Bremner wrote:
>> +/* Prior to NOTMUCH_FEATURE_LAST_MOD, messages did not
>> + * track modification revisions. Give all messages a
>> + * revision of 1.
>> + */
>> +if (new_features & NOTMUCH
Hi,
On Fri, 05 Jun 2015 19:28 +0200, David Bremner wrote:
> + /* Prior to NOTMUCH_FEATURE_LAST_MOD, messages did not
> + * track modification revisions. Give all messages a
> + * revision of 1.
> + */
> + if (new_features & NOTMUCH_FEATURE_LAST_MOD)
> +
Hi,
On Fri, 05 Jun 2015 19:28 +0200, David Bremner wrote:
> + /* Prior to NOTMUCH_FEATURE_LAST_MOD, messages did not
> + * track modification revisions. Give all messages a
> + * revision of 1.
> + */
> + if (new_features & NOTMUCH_FEATURE_LAST_MOD)
> +
From: Austin Clements
This adds a new document value that stores the revision of the last
modification to message metadata, where the revision number increases
monotonically with each database commit.
An alternative would be to store the wall-clock time of the last
modification of each message.
From: Austin Clements
This adds a new document value that stores the revision of the last
modification to message metadata, where the revision number increases
monotonically with each database commit.
An alternative would be to store the wall-clock time of the last
modification of each message.