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


From: vasylenko(at)uksatse(dot)org(dot)ua
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re:
Date: 2007-01-11 06:42:39
Message-ID: OF41BC4C79.AFC9FDE2-ONC2257260.0021E3EA-C2257260.0024D58E@UKCC.UKSATSE (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc

Dave and Andre, thank for your responses!

The JDBC driver needs the Primary Key in Select query to identify the row.
I was mistaken thinking of  doing without it,

ResultSet makes updates in Row  executing the

java.sql.Connection.prepareStatement("UPDATE holidays SET  "g_name" = ?
WHERE "id" = ?")
and  executeUpdate()

when user makes call ResultSet.updateRow() and "id" - the Primary Key in
database's table.  It's logicaly for me now....

The same is going on whe users call ResultSet.insertRow().
The only question presents, why the JDBCDriver developers want to find
PrimaryKey or oid field inside method "moveToInsertRow()"?
I think it mustn't be JDBCDriver problem.
It is the Postrgre server trouble or developers who use JDBCDriver.

I'm going to do in way Andre has recommended and use id field in SELECT
query as Dave has advised.



  • Re: at 2007-01-11 12:33:11 from Dave Cramer

pgsql-jdbc by date

Next:From: Deval kulshresthaDate: 2007-01-11 11:56:49
Subject: Test db connection to 'jdbc:postgresql://grid-master:5432/arco' ... Failed (1)
Previous:From: Kris JurkaDate: 2007-01-11 05:15:03
Subject: Re: Cannot create PoolableConnectionFactory

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