Skip site navigation (1) Skip section navigation (2)

BUG #2288: bad value for type timestamp using JDBC Type2 Driver version 8.1-405

From: "Jonathan Albert C(dot) Vallar" <jonathan(dot)vallar(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2288: bad value for type timestamp using JDBC Type2 Driver version 8.1-405
Date: 2006-02-28 03:51:20
Message-ID: 20060228035120.F0CE9F0B03@svr2.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      2288
Logged by:          Jonathan Albert C. Vallar
Email address:      jonathan(dot)vallar(at)gmail(dot)com
PostgreSQL version: 8.1.3
Operating system:   Centronix Linux
Description:        bad value for type timestamp using JDBC Type2 Driver
version  8.1-405
Details: 

My program reports "bad value for type timestamp" when I am accessing a
table with a field that is defined of type "Timestamp" through a java
program that uses the JDBC of postgres. The JDBC Driver is a type2 driver
with version, 8.1-405.

Below is the stack trace of the error:

Retrieve Operation failed on the BusinessObject Bad value for type timestamp
: [C(at)56c55d28  Exception: java.lang.NumberFormatException: Expected time to
be colon-separated, got ' Stack Trace:  java.lang.NumberFormatException:
Expected time to be colon-separated, got '  at
org.postgresql.jdbc2.TimestampUtils.loadCalendar(TimestampUtils.java:151)  
at org.postgresql.jdbc2.TimestampUtils.toTimestamp(TimestampUtils.java:307) 
 at
org.postgresql.jdbc2.AbstractJdbc2ResultSet.getTimestamp(AbstractJdbc2Result
Set.java:419)   at
org.postgresql.jdbc2.AbstractJdbc2ResultSet.getTimestamp(AbstractJdbc2Result
Set.java:2088)   at
com.crossworlds.connectors.JDBC.JDBCBOhandler.doContainerRetrieve(JDBCBOhand
ler.java:3697)   at
com.crossworlds.connectors.JDBC.JDBCBOhandler.doRecursiveRetrieve(JDBCBOhand
ler.java:3316)   at
com.crossworlds.connectors.JDBC.JDBCBOhandler.doRetrieve(JDBCBOhandler.java:
3265)   at
com.crossworlds.connectors.JDBC.JDBCBOhandler.doVerbFor(JDBCBOhandler.java:1
346)   at
com.crossworlds.cwconnectorapi.CWConnectorBOHandler.doVerbFor(CWConnectorBOH
andler.java:127)   at
CxCommon.BusinessObject.doVerbFor(BusinessObject.java:2128)   at
com.crossworlds.cwconnectorapi.CWConnectorBusObj.doVerbFor(CWConnectorBusObj
.java:126)   at
com.crossworlds.connectors.JDBC.JDBCConnectorAgent.pollForEvents(JDBCConnect
orAgent.java:1137)   at
AppSide_Connector.BusObjJavaInterface.poll(BusObjJavaInterface.java:355)  
at AppSide_Connector.AppCalls.poll(AppCalls.java:191)   at
AppSide_Connector.AgentBusinessObjectManager.poll(AgentBusinessObjectManager
.java:719)   at AppSide_Connector.AppPolling.poll(AppPolling.java:294)   at
AppSide_Connector.AppPolling.doPollingContinuousWait(AppPolling.java:556)  
at AppSide_Connector.AppPolling.run(AppPolling.java:121)   at
java.lang.Thread.run(Thread.java:513)  End of Stack Trace   SQLException
{2}]

The Schema of the table is:

(1 row)

wbi_db=> \d xworlds_events;
              Table "public.xworlds_events"
     Column     |            Type             | Modifiers
----------------+-----------------------------+-----------
 event_id       | bigint                      | not null
 connector_id   | character varying(40)       |
 object_key     | character varying(80)       | not null
 object_name    | character varying(40)       | not null
 object_verb    | character varying(40)       | not null
 event_priority | real                        | not null
 event_time     | timestamp without time zone |
 event_status   | integer                     |
 event_comment  | character varying           |


I have one record:

wbi_db=> select * from xworlds_events;
 event_id | connector_id | object_key |     object_name      | object_verb |
event_priority |        event_time         | event_status | event_comment
----------+--------------+------------+----------------------+-------------+
----------------+---------------------------+--------------+---------------
        1 | PostgreSQL   | 8100000000 | POS_to_SAP_1_WRAPPER | Create      |
             1 | 2006-02-27 19:51:22.58118 |            0 | Test
(1 row)


Is there a problem with the JDBC Driver? Specifically in the method
loadDriver?


Thanks in advance :)

Best Regards,

Jonathan

pgsql-bugs by date

Next:From: Abhilash KrishnanDate: 2006-02-28 09:24:35
Subject: BUG #2289: insert into tables not working
Previous:From: Tom LaneDate: 2006-02-27 21:58:38
Subject: Re: has_table/schema_privilige() returns incorrect info on temp tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group