|
Home > Archive > PostgreSQL JDBC > November 2005 > How to solve invalid input for tyep timestamp problem?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How to solve invalid input for tyep timestamp problem?
|
|
| Joost Kraaijeveld 2005-11-02, 7:23 am |
| Hi,
I want log4j to log in a PostgreSQL database. Log34j uses "2005-11-02
11:49:57,844" as it's timestamp format. I used TIMESTAMP as a columntype
but apparenty that is not the correct type:
java.sql.SQLException: ERROR: invalid input syntax for type timestamp:
"2005-11-02 11:49:57,844"
What should be the type I should use for the column?
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J.Kraaijeveld@Askesis.nl
web: www.askesis.nl
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly
| |
| Dave Cramer 2005-11-02, 7:23 am |
| What version of the driver are you using ?
Does log4j use prepared statements?
This is the right column, but the , between 57,844 is wrong, there
was a bug in the HEAD driver which would
have caused this if the answer to the first 2 questions is HEAD, and
yes.
If this doesn't solve your problem, then I suspect it is locale
related. The comma (,) is commonly used for the decimal
place in EU.
Dave
On 2-Nov-05, at 5:57 AM, Joost Kraaijeveld wrote:
> Hi,
>
> I want log4j to log in a PostgreSQL database. Log34j uses "2005-11-02
> 11:49:57,844" as it's timestamp format. I used TIMESTAMP as a
> columntype
> but apparenty that is not the correct type:
>
> java.sql.SQLException: ERROR: invalid input syntax for type timestamp:
> "2005-11-02 11:49:57,844"
>
> What should be the type I should use for the column?
>
>
> --
> Groeten,
>
> Joost Kraaijeveld
> Askesis B.V.
> Molukkenstraat 14
> 6524NB Nijmegen
> tel: 024-3888063 / 06-51855277
> fax: 024-3608416
> e-mail: J.Kraaijeveld@Askesis.nl
> web: www.askesis.nl
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql
.org so that
> your
> message can get through to the mailing list cleanly
>
>
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Joost Kraaijeveld 2005-11-02, 7:23 am |
| Hi Dave,
On Wed, 2005-11-02 at 07:19 -0500, Dave Cramer wrote:
> What version of the driver are you using ?
postgresql-8.0-313.jdbc3.jar
> Does log4j use prepared statements?
No, it does not in the JBoss supplied version (JBoss 4.0.3 / Log4J
1.2.8)
> This is the right column, but the , between 57,844 is wrong, there
> was a bug in the HEAD driver which would
> have caused this if the answer to the first 2 questions is HEAD, and
> yes.
Ah, ",". I should either take glasses or reset my screen resolution.
After replacing the format specifiers: yes, that solves the problem.
Thanks, for answering.
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J.Kraaijeveld@Askesis.nl
web: www.askesis.nl
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Kris Jurka 2005-11-08, 4:12 pm |
|
On Wed, 2 Nov 2005, Dave Cramer wrote:
> What version of the driver are you using ?
> Does log4j use prepared statements?
>
> This is the right column, but the , between 57,844 is wrong, there was a bug
> in the HEAD driver which would
> have caused this if the answer to the first 2 questions is HEAD, and yes.
>
Just for the record. The problem was in interval parsing, not timestamp,
and it is fixed now.
Kris Jurka
---------------------------(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
|
|
|
|
|