CachedRowSetImpl vs RowSet

[Alejandro Barrero]

I have been using CachedRowSetImpl because I remember reading that I cannot use RowSet after I close the connection. Now I am not sure. If my assumption correct. Could I use RowSet after clossing the connection if I create the Statement with RowSet.CONCUR_READ_ONLY?

[Shailesh Chandra]

Alejandro Barrero wrote: Could I use RowSet after clossing the connection if I create the Statement with RowSet.CONCUR_READ_ONLY?

Yes you can use rowset after closing connection, I tried it long back, check if this helps

http://ilovej2ee.blogspot.com/2008/01/using-cachedrowset-in-java.html


Thanks,
Shailesh

[Alejandro Barrero]

Thank you Shailesh.

[Alan Moor]

Um, yeah. If your RowSet was created from Statement tied to a Connection and you close the Connection, all the resources opened by that connection SHOULD be released. If you have a scrollable rowset, it is possible that the JDBC driver (incorrectly) has rows cached that you can use, but if you haven't retrieved all the rows, you won't be able to scroll past the last block retrieved.

If your intent is to disconnect the Rowset from the database connection, then you should use the disconneced rowset (CachedRowSetImpl).