Nic Ferrier wrote:
> Thomas O'Dowd writes:
>
>
> >>3) I think the transaction characteristics of the current patch are just
> >>fine and conform to the jdbc specification. The code should
> >>automatically close the resultset when a commit occurs. One thing that
> >>will be confusing is that noncursor based result sets will work accross
> >>commits, but cursor based ones won't. But I think that is reasonable.
> >
> >Sounds reasonable to me as long as its clear to the programmer what type
> >they are using. I definitely don't want to see the noncursor based
> >resultsets closed, but I can't see a better solution for cursor based
> >ones...
>
>
> How can we make clear what type of ResultSet is being used?
I suggest with ResultSet.CLOSE_CURSORS_AT_COMMIT (cursor method) vs
ResultSet.HOLD_CURSORS_OVER_COMMIT (old method). You can both request a
certain type when you create a Statement or PreparedStatement and get
the type of the resultset from the Statement or PreparedStatement.
Thanks,
Scott