Tom Lane wrote:
Luca Clementi <[EMAIL PROTECTED]> writes:
It seems that the to_timestamp does not work properly in this case,
when it comes to parsing the hours.
to_timestamp() is not very robust if the input doesn't exactly match
what it expects for the format string. I'm not sure if that's the
issue here, but have you tried just casting the string to timestamp?
That would use the standard timestamp input converter, which is
pretty flexible.
(BTW, there is definitely 0 hope of recognizing a timezone name that's
written in Chinese characters, unless maybe you fool around with the
timezone-abbreviations configuration file.)
I found the problem!!
to_timestamp(start_time, 'M DD, YYYY HH12:MI:SS')
^^^^^^
in the formatting string I have two spaces, while in the original there
is only one:
1 28, 2008 12:23:19 午後
So if I use: 'M DD, YYYY HH12:MI:SS' as a formatting string it works!
I wander how come if the formatting string doesn't match properly you
get such a bad behavior, would it better just a error?
PS: some e-mail clients do not render properly the spacing in my first
e-mail.
Thanks again for your help!!
Luca
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
