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

Re: bug in getTime after insertRow with postgresql-8.1-404.jdbc3.jar

From: "hpb(at)htl-steyr(dot)ac(dot)at" <hpb(at)htl-steyr(dot)ac(dot)at>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: "hpb(at)htl-steyr(dot)ac(dot)at" <hpb(at)htl-steyr(dot)ac(dot)at>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: bug in getTime after insertRow with postgresql-8.1-404.jdbc3.jar
Date: 2006-01-06 01:50:52
Message-ID: 43BDCCFC.6050105@htl-steyr.ac.at (view raw or flat)
Thread:
Lists: pgsql-jdbc
The data is inserted in the database correctly!
I was thinking about a workaround by doing another select. I didn't I 
posted in the newsgroup ;-)

hpb

Oliver Jowett schrieb:

> hpb(at)htl-steyr(dot)ac(dot)at wrote:
> 
>> 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());
> 
> 
> Is the data actually inserted to the database correctly?
> 
> If you re-query it via a different resultset, is it correct?
> 
> (IIRC, insertRow() directly updates the Java-side resultset without 
> requerying the DB, which is why I ask -- I suspect there will be a bug 
> in that update code)
> 
> -O


In response to

pgsql-jdbc by date

Next:From: Victor Pérez JuárezDate: 2006-01-06 02:43:49
Subject: appears twice in primary key constraint
Previous:From: Oliver JowettDate: 2006-01-06 00:58:46
Subject: Re: [IDLE in TRANSACTION] when I do TOP -c

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