From: | "hpb(at)htl-steyr(dot)ac(dot)at" <hpb(at)htl-steyr(dot)ac(dot)at> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | bug in getTime after insertRow with postgresql-8.1-404.jdbc3.jar |
Date: | 2006-01-05 12:39:31 |
Message-ID: | 43BD1383.8090702@htl-steyr.ac.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
hi,
I suspect, I bumpt into a bug with insertRow.
Here is my java code:
-------------------------------snipp-------------------------------
System.out.println("millisec before
update:"+((java.sql.Time)rs.getTime(dbAttribute)).getTime());
rs.updateTime(dbAttribute, new java.sql.Time( (
(java.util.Date)this.theValue).getTime()));
System.out.println("millisec after
update:"+((java.sql.Time)rs.getTime(dbAttribute)).getTime());
..
..
..
System.out.println("millisec before
insertRow:"+((java.sql.Time)this.db.rs.getTime("ist_von")).getTime());
this.db.rs.insertRow(); //write the actual insert row to table
System.out.println("millisec after
insertRow:"+((java.sql.Time)this.db.rs.getTime("ist_von")).getTime());
-------------------------------snipp-------------------------------
the output is
-------------------------------snipp-------------------------------
millisec before update:60000
millisec after update:60000
millisec before insertRow:60000
millisec after insertRow:3660000
-------------------------------snipp-------------------------------
what indicates that after the insertRow my timezone is added CET -> one
hour more -> 3600000 msec
if I use postgresql-8.0-314.jdbc3.jar
it behaves normal ->
-------------------------------snipp-------------------------------
millisec before update:60000
millisec after update:60000
millisec before insertRow:60000
millisec after insertRow:60000
-------------------------------snipp-------------------------------
thanks for any help
hpb
From | Date | Subject | |
---|---|---|---|
Next Message | Khaldoun Ateyeh | 2006-01-05 12:49:32 | Re: table full scan |
Previous Message | Roland Walter | 2006-01-05 12:15:17 | Re: table full scan |