| From: | Hannu Krosing <hannu(at)sid(dot)tm(dot)ee> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [DOCS] Use of 'now' |
| Date: | 2001-11-15 14:54:44 |
| Message-ID: | 3BF3D734.9020404@sid.tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roland Roberts | 2001-11-15 15:57:53 | Re: [PATCHES] Interchange |
| Previous Message | Calin Lukas | 2001-11-15 14:17:16 | Ann: Database Developing and Reporting System |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB SD | 2001-11-15 15:44:07 | Re: [HACKERS] Open Items (was: RE: [HACKERS] Beta going well) |
| Previous Message | Cameron Laird | 2001-11-15 14:21:20 | Re: Tcl C API documentation? |