The number of rows affected by an UPDATE statement are commonly used
to detect update conflicts. Statements like

UPDATE <table> SET <column> = <newValue> WHERE <column> = <oldValue>

or

UPDATE <table> SET <column> = <newValue> WHERE <timestamp> =
<oldTimestamp>

are used to detect conflicts. A row count of 0 means that the update
of the row failed because in the meantime it was updated by someone
else. This situation doesn't raise any database error and can
therefore only be detected in this way.


I couldn't understand how exactly the tests were done. I'm mainly
interested in knowing the difference between InterClient's and
JayBird's executeUpdate times for INSERT/UPDATE/DELETE statements.
If a significant (>10%) performance difference is still visible, how
would you explain that?

Best regards,
Stephan