From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 8047E431FB6 for ; Fri, 7 Dec 2012 08:52:28 -0800 (PST) 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 iTY2puAOzw8b for ; Fri, 7 Dec 2012 08:52:26 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by olra.theworths.org (Postfix) with ESMTP id C6E74431FAE for ; Fri, 7 Dec 2012 08:52:26 -0800 (PST) Received: from [192.168.23.207] (dsl254-070-154.nyc1.dsl.speakeasy.net [216.254.70.154]) by che.mayfirst.org (Postfix) with ESMTPSA id 3D34BF970; Fri, 7 Dec 2012 11:52:23 -0500 (EST) Message-ID: <50C21EC8.6020504@fifthhorseman.net> Date: Fri, 07 Dec 2012 11:52:24 -0500 From: Daniel Kahn Gillmor User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Icedove/17.0 MIME-Version: 1.0 To: David Bremner Subject: Re: [PATCH] TODO: date range queries - check References: <1354833276-6219-1-git-send-email-jani@nikula.org> <877gouine4.fsf@servo.finestructure.net> <871uf2ukat.fsf@zancas.localnet> In-Reply-To: <871uf2ukat.fsf@zancas.localnet> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: notmuch@notmuchmail.org 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: Fri, 07 Dec 2012 16:52:28 -0000 On 12/07/2012 07:19 AM, David Bremner wrote: > For specifying one-ended ranges, I find the current syntax OK-ish. It > would be reasonable to formulate a seperate TODO for supporting > things like date:2012-12-07 Out of curiosity, how does this syntax interact with timezones? If i send a mail in the wee hours of the 27th from the east coast of the US (GMT-0500) and jrollins reads it from the west coast of the US (GMT-0800) where it is still the 26th, should our notmuch queries behave differently when searching for this message? are we tracking the TZ of the Date: header in the database at all? does it make sense to take that into account for these queries? --dkg, posing questions he has no answers to