executeUpdate() returns 0 rows even though target DB has been updated

[BillyKrow]

My subject describes my problem exactly. I have an executeUpdate() command that updates an Orale database like:

int rows = statement.executeUpdate();
statement.close();

if (rows == 0) {
System.out.println("Zero rows updated
throw new MyException ("Zero rows were updated");
}

If I leave the check in, an exception is thrown and the database is eventually rolled back. If I take the check out then the database updates successfully. Is there any rare situations that executeUpdate could return 0 but still update successfully?

 

[sedj]

You have to remember that while the JavaDoc :
[ignore]

http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Statement.html#executeUpdate(java.lang.String)

[/ignore]

states that the int returned should be the number of rows affected, JDBC drivers can (in reality) implement the JDBC interfaces as they like. So if they return, for example, 0 for good updates, 1 for failures, then so be it. I expect your driver is not implementing the spec properly. I doubt its anything to worry about ....

--------------------------------------------------
Free Database Connection Pooling Software

http://www.primrose.org.uk

 

[BillyKrow]

Yes, I read something to this effect, that the driver may be the issue. It's strange though that I've never seen this problem in any other similar updateStatements.