Thread

1. timestamp('01/12/01') doesn't work in 7.2 beta4

   Henshall, Stuart - WCP <shenshall@westcountrypublications.co.uk> — 2001-12-13T17:49:15Z

   Hello,
   	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 have the timestamp('25/12/01') in clients that would be a pain to
   upgrade and was hoping to go to 7.2 seamlessly (and yes I do feel a dufous
   for not using spec approved CAST('25/12/01' AS timestamp) :) )
   - Stuart
   P.S. Please reply to me as well as list
   
   

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

   Tom Lane <tgl@sss.pgh.pa.us> — 2001-12-13T23:06:44Z

   "Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.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