Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 14F96431FD0 for ; Thu, 12 May 2011 01:40:08 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3njAft1x1Nc1 for ; Thu, 12 May 2011 01:40:04 -0700 (PDT) Received: from imarko.xen.prgmr.com (imarko.xen.prgmr.com [72.13.95.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 37D30431FB6 for ; Thu, 12 May 2011 01:40:04 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=zsu.kismala.com) by imarko.xen.prgmr.com with esmtp (Exim 4.75) (envelope-from ) id 1QKRR8-0001KT-MZ; Thu, 12 May 2011 01:40:01 -0700 From: Istvan Marko To: Stewart Smith Subject: Re: storing From and Subject in xapian References: <87zkmwsc2d.fsf@servo.factory.finestructure.net> <87ei45rjm4.fsf@flamingspork.com> Date: Thu, 12 May 2011 01:39:58 -0700 In-Reply-To: <87ei45rjm4.fsf@flamingspork.com> (Stewart Smith's message of "Wed, 11 May 2011 13:39:31 +1000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Cc: notmuch@notmuchmail.org, Austin Clements X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2011 08:40:08 -0000 Stewart Smith writes: > Would it be possible to progressively fill the DB with the new data? > > i.e. > > if Subject/From not in db for message > add Subject/From for this message to DB. I started looking into this but then realized that notmuch search opens the database in read-only mode so it cannot make updates. It might be desirable to keep it that way for safety and locking reasons. -- Istvan