(2.6.1) Behavior change for update statement affecting no rows

For the past year or two we’ve had this statement running without issue:

update ORGANIZATION set created = 0 where created is NULL

As of 2.6.1, this now produces the following warning as an exception:

[IBM][CLI Driver][DB2/LINUXX8664] SQL0100W  No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table.  SQLSTATE=02000

Is there a way to restore the original behavior? If not, how should we detect warnings like this to distinguish them from actual errors?

This seems to have also worked with 2.6.0. In the meantime, we have locked our version to 2.5.3 even though 2.5.1 is marked as the current release. Not sure what’s up there.

Thanks!

[rbetjes]

Ibm_db should definately return succes on warnings because the sql statement is executed succesfully (in our case at least). There is no reason not to return the fetched data. As for the warning itself, it could be helpfull to have access to it. Just not as an error. To be fair, we are using a 3rd party package that acts as a wrapper around ibm_db. That package now throws an exception.

[John-Kryspin]

Thanks for opening this @dongryphon I agree that it should by default not throw an exception for warning, but it can be an option when creating the DB2 connection.

The SQL is executed successfully, and the warning is not really an error, but rather more information. For now we are going to stay on version 2.5.3.