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: | brong(at)h-r-s(dot)com, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #656: timestamp function generates parsing errors when |
Date: | 2002-06-02 21:55:43 |
Message-ID: | 200206022155.g52LthI09013@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tom Lane wrote:
> pgsql-bugs(at)postgresql(dot)org writes:
> > See the following session examples using the form given in the documentation. 'select timestamp(now());' fails similarly.
>
> I'm afraid you've got bit by our continuing pursuit of SQL standard
> compliance. The 7.2 release notes do point out:
>
> Observe the following incompatibilities:
> * The timestamp() function is no longer available. Use timestamp 'string' instead, or CAST.
>
> but I notice that the last two examples in Table 4-17 "Date/Time Functions"
> didn't get fixed. (AFAICT there are no other places in current
> documentation that claim you can do that.)
I have removed those two timestamp() entries from the SGML table; patch
attached. I don't see any need to mention casting in that table. In
fact, timestamp() was the only conversion function mentioned in that
table.
--
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
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-02 22:38:02 | Re: PQescapeString and PQescapeBytea not exported during win |
Previous Message | Bruce Momjian | 2002-06-02 20:45:12 | Re: Bug #655: win32 client and bytea column |