Postgres Pro
Downloads
Home   >   mailing lists

Thread: timestamp exception in driver

timestamp exception in driver

From
"Jan Blok"
Date:
Hi,

I encounter the following bug in the postgresql driver...(it seems that
the driver 7.3dev not supports a timestamp which is inside the database)

Bad Timestamp Format at 16 in 0001-01-01 09:00 BC
        at
org.postgresql.jdbc2.ResultSet.toTimestamp(ResultSet.java:1705)
        at
org.postgresql.jdbc2.ResultSet.getTimestamp(ResultSet.java:398)
        at nl.profdata.syne.ContentList.makeRows(ContentList.java:438)
        at nl.profdata.syne.ContentList.<init>(ContentList.java:68)
        at
nl.profdata.syne.ContentManager.getContentByQuery(ContentManager.java
:260)
        at Planner.getAvailebleTimes(Planner.java:141)
        at Planner.main(Planner.java:41)
SQL from the exception select ea.start_time,ea.end_time, -1 as
product_id,e.empl oyee_id,0 as customer_id,pe.priority from employees
e,employee_avail ea,product_ employee pe where e.employee_id =
pe.employee_id and pe.product_id = 1003 and e. employee_id =
ea.employee_id and ea.weekday = 4 and e.supplier_id = 1001 order b y
e.employee_id,ea.start_time

Re: timestamp exception in driver

From
Thomas O'Dowd
Date:
Hi Jan,

It seems we don't like the optional 'BC' bit :( I'll try grab some time
today to have a closer look at it.

Cheers,

Tom.

On Mon, May 20, 2002 at 09:35:09PM +0200, Jan Blok wrote:
> Hi,
>
> I encounter the following bug in the postgresql driver...(it seems that
> the driver 7.3dev not supports a timestamp which is inside the database)
>
> Bad Timestamp Format at 16 in 0001-01-01 09:00 BC
>         at
> org.postgresql.jdbc2.ResultSet.toTimestamp(ResultSet.java:1705)
>         at
> org.postgresql.jdbc2.ResultSet.getTimestamp(ResultSet.java:398)
>         at nl.profdata.syne.ContentList.makeRows(ContentList.java:438)
>         at nl.profdata.syne.ContentList.<init>(ContentList.java:68)
>         at
> nl.profdata.syne.ContentManager.getContentByQuery(ContentManager.java
> :260)
>         at Planner.getAvailebleTimes(Planner.java:141)
>         at Planner.main(Planner.java:41)
> SQL from the exception select ea.start_time,ea.end_time, -1 as
> product_id,e.empl oyee_id,0 as customer_id,pe.priority from employees
> e,employee_avail ea,product_ employee pe where e.employee_id =
> pe.employee_id and pe.product_id = 1003 and e. employee_id =
> ea.employee_id and ea.weekday = 4 and e.supplier_id = 1001 order b y
> e.employee_id,ea.start_time
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

--
Thomas O'Dowd. - Nooping - http://nooper.com
tom@nooper.com - Testing - http://nooper.co.jp/labs

Re: timestamp exception in driver

From
Dave Cramer
Date:
Is that a real time? I'm not sure that java supports times BC?

Does anyone know?

Dave

On Mon, 2002-05-20 at 15:35, Jan Blok wrote:
> Hi,
>
> I encounter the following bug in the postgresql driver...(it seems that
> the driver 7.3dev not supports a timestamp which is inside the database)
>
> Bad Timestamp Format at 16 in 0001-01-01 09:00 BC
>         at
> org.postgresql.jdbc2.ResultSet.toTimestamp(ResultSet.java:1705)
>         at
> org.postgresql.jdbc2.ResultSet.getTimestamp(ResultSet.java:398)
>         at nl.profdata.syne.ContentList.makeRows(ContentList.java:438)
>         at nl.profdata.syne.ContentList.<init>(ContentList.java:68)
>         at
> nl.profdata.syne.ContentManager.getContentByQuery(ContentManager.java
>:260)
>         at Planner.getAvailebleTimes(Planner.java:141)
>         at Planner.main(Planner.java:41)
> SQL from the exception select ea.start_time,ea.end_time, -1 as
> product_id,e.empl oyee_id,0 as customer_id,pe.priority from employees
> e,employee_avail ea,product_ employee pe where e.employee_id =
> pe.employee_id and pe.product_id = 1003 and e. employee_id =
> ea.employee_id and ea.weekday = 4 and e.supplier_id = 1001 order b y
> e.employee_id,ea.start_time
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
>