Howdy, You don't have to close a result set if you're closing the statement right away and the result set is the only one associated with the statement... And in no case can closing the result set explicitly hurt performance.
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Greg Ward [mailto:[EMAIL PROTECTED] >Sent: Thursday, September 04, 2003 10:05 AM >To: Tomcat Users List; [EMAIL PROTECTED] >Subject: Re: Memory leaks? > >On 03 September 2003, Jim Lynch said: >> OK, that's probably what's going on. I know I should close Statements >> and Connections and do normally but I'm fairly certain I've some out >> there dangling. I didn't know you had to close ResultSets, however. >> Glad to know that. > >You don't have to close ResultSets -- check the JDBC docs: > > http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Statement.html#close() > >(Closing a Statement also closes any open ResultSets associated with >that Statement.) > > Greg > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
