Re: timestamp('01/12/01') doesn't work in 7.2 beta4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>
Cc: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: timestamp('01/12/01') doesn't work in 7.2 beta4
Date: 2001-12-13 23:06:44
Message-ID: 512.1008284804@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk> writes:
> The timestamp('25/12/01') would return a timestamp in 7.1, how ever
> in 7.2 beta 4 select "timestamp"('25/12/01') is needed, although select
> timestamptz('25/12/01') works. Is this change intentional and if so is there
> a way of getting the old functionality to work?

I'm afraid you're stuck. TIMESTAMP(n) is now a type name, per SQL92
standard, and getting the parser to treat TIMESTAMP(somethingotherthan
anintegerconstant) as a function call instead does not seem real
practical.

The only bright spot is that as we get closer to full SQL92 compliance,
these sorts of gotchas should become less frequent. But this one is
surely not the last.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dominic J. Eidson 2001-12-13 23:17:55 Re: How to increase shared mem for PostgreSQL on FreeBSD
Previous Message Fran Fabrizio 2001-12-13 22:51:57 Re: storing intermediate results from recursive plpgsql