Austin Clements writes:
> This series modifies our database representation of messages that have
> been referenced by other messages, but for which we don't have the
> message itself. Currently, we store this information as Xapian
> metadata, but this has several downsides for performance and
>
Austin Clements writes:
> This series modifies our database representation of messages that have
> been referenced by other messages, but for which we don't have the
> message itself. Currently, we store this information as Xapian
> metadata, but this has several downsides for performance and
>
On Sat, 04 Oct 2014, Tomi Ollila wrote:
> On Fri, Oct 03 2014, Austin Clements wrote:
>
>> This series modifies our database representation of messages that have
>> been referenced by other messages, but for which we don't have the
>> message itself. Currently, we store this information as Xapia
On Sat, 04 Oct 2014, Tomi Ollila wrote:
> On Fri, Oct 03 2014, Austin Clements wrote:
>
>> This series modifies our database representation of messages that have
>> been referenced by other messages, but for which we don't have the
>> message itself. Currently, we store this information as Xapia
On Fri, Oct 03 2014, Austin Clements wrote:
> This series modifies our database representation of messages that have
> been referenced by other messages, but for which we don't have the
> message itself. Currently, we store this information as Xapian
> metadata, but this has several downsides fo
On Fri, Oct 03 2014, Austin Clements wrote:
> This series modifies our database representation of messages that have
> been referenced by other messages, but for which we don't have the
> message itself. Currently, we store this information as Xapian
> metadata, but this has several downsides fo
This series modifies our database representation of messages that have
been referenced by other messages, but for which we don't have the
message itself. Currently, we store this information as Xapian
metadata, but this has several downsides for performance and
complexity and results in hard-to-fi
This series modifies our database representation of messages that have
been referenced by other messages, but for which we don't have the
message itself. Currently, we store this information as Xapian
metadata, but this has several downsides for performance and
complexity and results in hard-to-fi
