From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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 16:39:16 |
Message-ID: | 200111151639.fAFGdGb03603@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
> > 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?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Roland Roberts | 2001-11-15 16:49:12 | PL/pgSQL examples NOT involving functions |
Previous Message | Tom Lane | 2001-11-15 16:36:16 | Re: [DOCS] Use of 'now' |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2001-11-15 16:52:05 | Re: handling exceptions, really not simple... :-(( |
Previous Message | Tom Lane | 2001-11-15 16:36:16 | Re: [DOCS] Use of 'now' |