Daniel John Debrunner (JIRA) wrote:
Agreed, it's the same issue in my mind, and allowing such a row in a ResultSet would be wrong. I believe after an update the row in the ResultSet must reflect the state of the row in the database. Hence, like Oracle, Derby should perform the equivalent of a refreshRow.
I think such an implementation kind of blurs the concept of sensitivity. You get a result set that is sensitive to some, but not all, changes performed by other statements in the same transaction. The available metadata for a result set, does not provide a way to describe such behavior. This whole discussion makes me think that the only sensible way to implement an insensitive result set is to not make own changes visible. At least, that would give a clean implementation with a behavior that is easy to understand.
-- Øystein
