Quoth David Bremner on Aug 23 at 8:58 pm:
> Austin Clements writes:
>
> >>> @@ -1048,7 +1164,8 @@ notmuch_database_get_version (notmuch_database_t
> >>> *notmuch)
> >>> notmuch_bool_t
> >>> notmuch_database_needs_upgrade (notmuch_database_t *notmuch)
> >>> {
> >>> -return notmuch->needs_
Austin Clements writes:
> Quoth David Bremner on Aug 23 at 8:58 pm:
>> Austin Clements writes:
>>
>> >>> @@ -1048,7 +1164,8 @@ notmuch_database_get_version (notmuch_database_t
>> >>> *notmuch)
>> >>> notmuch_bool_t
>> >>> notmuch_database_needs_upgrade (notmuch_database_t *notmuch)
>> >>>
Austin Clements writes:
> Quoth David Bremner on Aug 23 at 8:58 pm:
>> Austin Clements writes:
>>
>> >>> @@ -1048,7 +1164,8 @@ notmuch_database_get_version (notmuch_database_t
>> >>> *notmuch)
>> >>> notmuch_bool_t
>> >>> notmuch_database_needs_upgrade (notmuch_database_t *notmuch)
>> >>>
Quoth David Bremner on Aug 23 at 8:58 pm:
> Austin Clements writes:
>
> >>> @@ -1048,7 +1164,8 @@ notmuch_database_get_version (notmuch_database_t
> >>> *notmuch)
> >>> notmuch_bool_t
> >>> notmuch_database_needs_upgrade (notmuch_database_t *notmuch)
> >>> {
> >>> -return notmuch->needs_
Austin Clements writes:
>>> @@ -1048,7 +1164,8 @@ notmuch_database_get_version (notmuch_database_t
>>> *notmuch)
>>> notmuch_bool_t
>>> notmuch_database_needs_upgrade (notmuch_database_t *notmuch)
>>> {
>>> -return notmuch->needs_upgrade;
>>> +return notmuch->mode == NOTMUCH_DATABASE_
On Sat, 23 Aug 2014, David Bremner wrote:
> Austin Clements writes:
>>
>> +/* Bit mask of features used by this database. Features are
>> + * named, independent aspects of the database schema. This is a
>> + * bitwise-OR of NOTMUCH_FEATURE_* values (below). */
>> +unsigned int
Austin Clements writes:
>>> @@ -1048,7 +1164,8 @@ notmuch_database_get_version (notmuch_database_t
>>> *notmuch)
>>> notmuch_bool_t
>>> notmuch_database_needs_upgrade (notmuch_database_t *notmuch)
>>> {
>>> -return notmuch->needs_upgrade;
>>> +return notmuch->mode == NOTMUCH_DATABASE_
Quoth Jani Nikula on Aug 23 at 7:02 pm:
> On Fri, 01 Aug 2014, Austin Clements wrote:
> > Previously, our database schema was versioned by a single number.
> > Each database schema change had to occur "atomically" in Notmuch's
> > development history: before some commit, Notmuch used version N, a
On Fri, 01 Aug 2014, Austin Clements wrote:
> Previously, our database schema was versioned by a single number.
> Each database schema change had to occur "atomically" in Notmuch's
> development history: before some commit, Notmuch used version N, after
> that commit, it used version N+1. Hence,
On Sat, 23 Aug 2014, David Bremner wrote:
> Austin Clements writes:
>>
>> +/* Bit mask of features used by this database. Features are
>> + * named, independent aspects of the database schema. This is a
>> + * bitwise-OR of NOTMUCH_FEATURE_* values (below). */
>> +unsigned int
Quoth Jani Nikula on Aug 23 at 7:02 pm:
> On Fri, 01 Aug 2014, Austin Clements wrote:
> > Previously, our database schema was versioned by a single number.
> > Each database schema change had to occur "atomically" in Notmuch's
> > development history: before some commit, Notmuch used version N, a
Austin Clements writes:
>
> +/* Bit mask of features used by this database. Features are
> + * named, independent aspects of the database schema. This is a
> + * bitwise-OR of NOTMUCH_FEATURE_* values (below). */
> +unsigned int features;
Should we be using a fixed size intege
Austin Clements writes:
>
> +/* Bit mask of features used by this database. Features are
> + * named, independent aspects of the database schema. This is a
> + * bitwise-OR of NOTMUCH_FEATURE_* values (below). */
> +unsigned int features;
Should we be using a fixed size intege
On Fri, 01 Aug 2014, Austin Clements wrote:
> Previously, our database schema was versioned by a single number.
> Each database schema change had to occur "atomically" in Notmuch's
> development history: before some commit, Notmuch used version N, after
> that commit, it used version N+1. Hence,
Previously, our database schema was versioned by a single number.
Each database schema change had to occur "atomically" in Notmuch's
development history: before some commit, Notmuch used version N, after
that commit, it used version N+1. Hence, each new schema version
could introduce only one chan
Previously, our database schema was versioned by a single number.
Each database schema change had to occur "atomically" in Notmuch's
development history: before some commit, Notmuch used version N, after
that commit, it used version N+1. Hence, each new schema version
could introduce only one chan
16 matches
Mail list logo
