After ResultSet.close()

ResultSet.close() is going to release any internal resources used by the ResultSet used to maintain the rows/columns returned from a query..

Calling ResultSet.close() on a closed ResultSet is guaranteed to be a no-op (and is clarified to do so in the JDBC 4.0 spec) We also added an isClosed() method to the ResultSet interface in JDBC 4.0.

Setting the ResultSet object to null will have some benefits depending on the scope of the object

lanceaa at 2007-7-13 18:56:15 >

> After given ResultSet is closed (via its .close()

> method), should I write

> rs = null; in order to ensure that it will be

> cleaned? or the close() method sets the ResultSet to

> null itself?

Here is a helpful tip.

Java != C++

Thank you.

Stop worrying about setting things to null. It doesn't do **** all. Just close your resources properly and when your objects go out of scope the garbage collector can do it's thing.

darteda at 2007-7-13 18:56:15 >