From: Tom Lane <tgl@sss.pgh.pa.us>
To: Luca Clementi <lclement@ucsd.edu>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problem with the to_timestamp function
Date: Thu, 31 Jan 2008 01:04:01 -0500
Message-ID: <751.1201759441@sss.pgh.pa.us> (raw)
In-Reply-To: <47A12CCB.1000807@ucsd.edu>
References: <47A10A1D.5020408@ucsd.edu>
<27257.1201739170@sss.pgh.pa.us>
<47A12CCB.1000807@ucsd.edu>
Luca Clementi <lclement@ucsd.edu> writes:
> 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?
Yeah, it should either do something reasonable or throw an error.
Improving to_timestamp's handling of such cases is on the TODO list.
In the meantime, though, the standard input converter is a whole lot
more flexible for slightly-out-of-spec input ... so I ask again,
do you really need to_timestamp at all?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, lclement@ucsd.edu
Subject: Re: Problem with the to_timestamp function
In-Reply-To: <751.1201759441@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox