Received: from mx99.openu.ac.il (arbel.openu.ac.il [147.233.32.4]) by hub.org (8.9.2/8.9.1) with ESMTP id GAA27399 for ; Tue, 30 Mar 1999 06:57:37 -0500 (EST) (envelope-from herouth@oumail.openu.ac.il) Received: from talmon.openu.ac.il (talmon.openu.ac.il [147.233.32.11]) by mx99.openu.ac.il (Postfix) with ESMTP for id 68D354B49E; Tue, 30 Mar 1999 11:57:36 +0000 (Asia/Jerusalem) Received: from [147.233.148.140] (1164.pc.openu.ac.il) by talmon.openu.ac.il (Netscape Messaging Server 3.54) with ESMTP id AAA1ABC for ; Tue, 30 Mar 1999 13:59:21 +0200 X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 30 Mar 1999 13:59:14 +0200 To: pgsql-sql@postgreSQL.org From: Herouth Maoz Subject: RE: [SQL] indexing a datetime by date At 06:07 +0200 on 30/03/1999, Jackson, DeJuan wrote: > > Part of the problem is that PostgreSQL Assumes that a functions value will > change each time it is required, therefore automatic table scan and the > function is called for each row. > Try using 'now'::date instead of now()::date How about using the ANSI standard CURRENT_DATE instead of either? It's already of type date. Or is it considered a function call? Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma