Hello and thank you.
I wrote a test case that is working correctly as expected. I'm not
able to reproduce the issue unfortunetly:-(
I also looked into the JDBC Driver source code and I didn't find
anything reasonable. The sources are the same for JDBC3 and JDBC3G.
So, I would like to close this issue and I'll investigate the problem more.
Thank you very much for your help!
Have a nice day,
On Jan 7, 2008 3:55 AM, Kris Jurka <books(at)ejurka(dot)com> wrote:
> On Sun, 30 Dec 2007, Hadraba Petr wrote:
> > I have a global PreparedStatement pStmt that handles the UPDATE
> > statement.
> > In for-cycle I'm doing the following:
> > - prepare values for the UPDATE
> > - call pStmt.clearParameters();
> > - call pStmt.setObject(paramOrderID, paramValue) for each value with
> > the right paramID and value
> > - call pStmt.addbatch();
> > After the for-cycle I'm calling the pStmt.executeBatch(); and
> > pStmt.close();
> > Please note, no Exceptions are thrown — the SQL code is correct and no
> > primary key nor foreign key valoations are occuring.
> > I'm able to post full source code and more info.
> Please post a full test case. I don't see any reason why Jdbc3 vs Jdbc3g
> would be any different.
> Kris Jurka
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
In response to
pgsql-jdbc by date
|Next:||From: mp.rajkhowa||Date: 2008-01-15 09:44:36|
|Subject: Updation is not commiting|
|Previous:||From: Kris Jurka||Date: 2008-01-15 07:27:46|
|Subject: Re: Patch for Statement.getGeneratedKeys()|