1 Return-Path: <james@jameswestby.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 34564431FAE
\r
6 for <notmuch@notmuchmail.org>; Fri, 18 Dec 2009 13:24:25 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id TZ3Pl9WNgIwv for <notmuch@notmuchmail.org>;
\r
11 Fri, 18 Dec 2009 13:24:24 -0800 (PST)
\r
12 Received: from jameswestby.net (jameswestby.net [89.145.97.141])
\r
13 by olra.theworths.org (Postfix) with ESMTP id DCA69431FBF
\r
14 for <notmuch@notmuchmail.org>; Fri, 18 Dec 2009 13:24:23 -0800 (PST)
\r
15 Received: from cpc4-aztw22-2-0-cust59.aztw.cable.virginmedia.com
\r
16 ([94.169.116.60] helo=flash)
\r
17 by jameswestby.net with esmtpa (Exim 4.69)
\r
18 (envelope-from <james@jameswestby.net>)
\r
19 id 1NLkJC-0005zZ-Vr; Fri, 18 Dec 2009 21:24:23 +0000
\r
20 Received: by flash (Postfix, from userid 1000)
\r
21 id 9155F6E546A; Fri, 18 Dec 2009 21:24:17 +0000 (GMT)
\r
22 From: James Westby <jw+debian@jameswestby.net>
\r
23 To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
\r
24 In-Reply-To: <873a38ypg5.fsf@yoom.home.cworth.org>
\r
25 References: <87oclwrtqa.fsf@jameswestby.net>
\r
26 <874onoysrl.fsf@yoom.home.cworth.org> <87my1grrdi.fsf@jameswestby.net>
\r
27 <873a38ypg5.fsf@yoom.home.cworth.org>
\r
28 Date: Fri, 18 Dec 2009 21:24:17 +0000
\r
29 Message-ID: <87ljh0rn5q.fsf@jameswestby.net>
\r
31 Content-Type: text/plain; charset=us-ascii
\r
32 Subject: Re: [notmuch] Missing messages breaking threads
\r
33 X-BeenThere: notmuch@notmuchmail.org
\r
34 X-Mailman-Version: 2.1.12
\r
36 List-Id: "Use and development of the notmuch mail system."
\r
37 <notmuch.notmuchmail.org>
\r
38 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
39 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
40 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
41 List-Post: <mailto:notmuch@notmuchmail.org>
\r
42 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
43 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
44 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
45 X-List-Received-Date: Fri, 18 Dec 2009 21:24:25 -0000
\r
47 On Fri, 18 Dec 2009 12:52:58 -0800, Carl Worth <cworth@cworth.org> wrote:
\r
48 > On Fri, 18 Dec 2009 19:53:13 +0000, James Westby <jw+debian@jameswestby.net> wrote:
\r
49 > Oh, I was assuming you wouldn't index any text. The UI can add "missing
\r
50 > message" for a document with no filename, for example.
\r
54 > > So, to summarise, I should first look at storing filesizes, then
\r
55 > > the collision code to make it index further when the filesize grows,
\r
56 > > and then finally the code to add documents for missing messages?
\r
58 > Some of the code areas to be touched will be changing soon, (at least as
\r
59 > far as when filenames appear and disappear). Hopefully I'll have
\r
60 > something posted for that sooner rather than later to avoid having to
\r
61 > redo too much work.
\r
63 That would be great. I'm learning all the code anyway, so there's not
\r
64 a whole lot of knowledge being thrown away.
\r
66 I've just sent an initial cut at the fist step.
\r
68 > > The only thing I am unclear on is how to handle existing databases?
\r
69 > > Do we have any concept of versioning? Or should I just assume that
\r
70 > > filesize: may not be in the document and act appropriately?
\r
72 > My current, outstanding patch is going to be the first trigger for a
\r
73 > "flag day" where we'll all need to rewrite our databases.
\r
75 > We don't have any concept of versioning yet, but it would obviously be
\r
76 > easy to have a new version document with an increasing integer.
\r
78 > But even with my current patch I'm considering doing a graceful upgrade
\r
79 > of the database in-place rather than making the user do something like a
\r
80 > dump, delete, rebuild, restore. That would give a much better experience
\r
81 > than "Your database is out-of-date, please rebuild it", so we'll see if
\r
82 > I pursue that in the end.
\r
84 That sounds nice, I'd certainly prefer this sort of thing as it evolves.
\r