Forums Register Login

close on CachedRowSet

+Pie Number of slices to send: Send
I have some code that had lots of (oracle) database accesses. I encountered 'too many open cursors' errors. Although i checked thoughroghly, i think i was missing out on closing some resources. I changed my source code to have a single method that executed queries and returned a CachedRowSet. My question is, being a disconnected resultset is it absolutely necessary to close the CachedRowSet? I did close the Statement objects and ResultSet objects from which i got the CachedRowSet object. Wont just resetting the old CachedRowSet with a new one be ok? Something like:-



Thanks
Neville
+Pie Number of slices to send: Send
having scaned the documentation and example for cached row set, it appears to be a hybrid of a statement and result set all in one.
I think it deffinatley needs closing.
Ever since I found this suit I've felt strange new needs. And a tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 1170 times.
Similar Threads
Closing Connection Which way ????
CachedRowSet not populating?
CachedRowSet is an abstract class
Selecting option in second selectOneMenu not setting property value
CachedRowSet is abstract; cannot be instantiated?
More...

All times above are in ranch (not your local) time.
The current ranch time is
Apr 16, 2024 05:14:57.