From: Hannu Krosing <hannu@sid.tm.ee>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Thomas Lockhart <lockhart@fourpalms.org>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: [DOCS] Use of 'now'
Date: Thu, 15 Nov 2001 19:54:44 +0500
Message-ID: <3BF3D734.9020404@sid.tm.ee> (raw)
References: <200111151639.fAFGdGb03603@candle.pha.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: hannu@sid.tm.ee, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, peter_e@gmx.net, lockhart@fourpalms.org, pgsql-hackers@postgresql.org
Subject: Re: [DOCS] Use of 'now'
In-Reply-To: <3BF3D734.9020404@sid.tm.ee>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox