Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAEGAJm29365 for ; Wed, 14 Nov 2001 11:10:19 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id fAEGAEu13530; Wed, 14 Nov 2001 11:10:14 -0500 (EST) From: Bruce Momjian Message-Id: <200111141610.fAEGAEu13530@candle.pha.pa.us> Subject: Re: Use of 'now' In-Reply-To: <3BF27B79.3F28F6D3@fourpalms.org> "from Thomas Lockhart at Nov 14, 2001 02:11:05 pm" To: lockhart@fourpalms.org Date: Wed, 14 Nov 2001 11:10:14 -0500 (EST) CC: Vince Vielhaber , Tom Lane , PostgreSQL-documentation X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200111/35 X-Sequence-Number: 1108 > Regarding the TIME data type: there was never a reserved value defined > for that type, so the feature was never available for it. Since > 'current' and 'now' are synonymous, it is a one-liner to add recognition > of 'current' to that type. I've got patches... You know I am totally lost with the date/time stuff. I am just pointing out stuff and guessing. Please do whatever you think is appropriate. Thanks. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026