In my JDBCR4 project, I thought I'd gotten rid of an issue with
undesired record locking in a CONCUR_UPDATABLE TYPE_SCROLL_SENSITIVE
But I was wrong.
The idea is to hold the result set, but not lock any record until
actually ready to update it.
I thought I could avoid record locks by positioning the result set's
cursor to "beforeFirst" or "afterLast." But it seems that even though
that theoretically places the cursor "not on a record," in practice, I'm
still holding a record lock.
I just now verified that the same thing happens when accessing the file
from Java, and worse, that the lock on the "current record" also remains
active if I "moveToInsertRow()."
I'd rather not have to open the main result set as CONCUR_READ_ONLY,
then open a separate CONCUR_UPDATABLE result set when I want the record
lock, but it's beginning to look like I'm stuck with exactly that,
unless there's some way through JDBC to get CONCUR_UPDATABLE result set
to release its lock without closing it outright.