From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Jonathan Vallar <jonathan(dot)vallar(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Bad Value for Data Type Timestamp |
Date: | 2006-02-28 17:57:31 |
Message-ID: | 76A61917-5AAB-4CFE-AE31-9E89DC126D08@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hmmmm.... that's strange. This must be in the output format, or some
other error.
Internally timestamps are stored as seconds. Is there an output
format that formats with a space between seconds and minutes ?
Dave
On 28-Feb-06, at 12:04 PM, Kris Jurka wrote:
>
>
> On Tue, 28 Feb 2006, Dave Cramer wrote:
>
>> What you sent as sample data is formatted correctly. So the only
>> thing I can think of is that the mapping of the columns is not
>> correct.
>
> Actually what he sent as sample data contained a space before the
> seconds field, "2006-02-27 19:51: 22.58118". I don't know how this
> got into the data because it gets rejected if you try and input it.
>
> jurka=# select '2006-02-27 19:51: 22.58118'::timestamp;
> ERROR: invalid input syntax for type timestamp: "2006-02-27 19:51:
> 22.58118"
>
> Jonathan, are you sure the data coming back from psql has a space
> in it? Any idea how you got into that state?
>
> Kris Jurka
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-02-28 18:18:36 | Re: Bad Value for Data Type Timestamp |
Previous Message | Kris Jurka | 2006-02-28 17:04:36 | Re: Bad Value for Data Type Timestamp |