Message-ID: <3BF3D734.9020404@sid.tm.ee>
Date: Thu, 15 Nov 2001 19:54:44 +0500
From: Hannu Krosing <hannu@sid.tm.ee>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:0.9.4) Gecko/20011019 Netscape6/6.2
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
CC: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>,
	Thomas Lockhart <lockhart@fourpalms.org>,
	PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: [DOCS] Use of 'now'
References: <200111151639.fAFGdGb03603@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Bruce Momjian wrote:

>>>I don't think this is a good idea.  If someone really relied on 'current'
>>>for his application, substituting 'now' for it is not going to make things
>>>better.  If it's done silently it will definitely make things worse.
>>>
>>I hadn't thought about it, but I believe Peter is right.  Rejecting
>>'current' is better than silently translating it to 'now'.  We have
>>removed this feature and we shouldn't try to paper over the fact.
>>
>
>My only question is how many people were using current thinking it
>functioned as 'now'?  Was current ever a desired feature?
>
The only times I have used current were by mistake when PG interpreted 
something
starting with current as current. I suspect that everybody who has been 
using current
thinking it functions as 'now' has either found out it does not or does 
not really care ;)
-----------
Hannu