Re: executeUpdate returned value
Posted by: Ledion B
Date: May 13, 2005 11:45PM

Hey Mark

I think it just boils down to what updated means, which could be 2 as you've alluded. I always thought that the records that matched the condition but did not change would not be updated, for optimization purposes (as you mentioned), and therefore not be considered updated. The number of changed records is what I would cautiosly say "important information" (not just because I need it) for the update to return, because you can find the number of matched rows with a select. Anyways, thanks for your effort and input.

Current, I am using the workaround that I mentioned, it would make the application more portable too.


Options: ReplyQuote

Written By
May 13, 2005 05:10PM
Re: executeUpdate returned value
May 13, 2005 11:45PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.