Originally posted by adeel ansari: may be this mySQL driver problem. refer this
The problem you refer to is not really a problem but due to the type of table selected which does not have transaction support.
It would appear as if the ResultSet object is just a staging area that keeps tabs on all the objects retrieved and re-writes them when updating. So if I don't update timestamp it just re-writes the old value.
I don't want this to happen and I don't want to update the timestamp on the client as the time may not be the same as the server. Is there a way to force the timestamp field to be updated or a way to remove it from the rowset?
Joined: Apr 20, 2004
I managed to get past this issue by setting the timestamp = null before the updateRow() statement