This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hallo, is it a general solution to always close the Statement- and ResultSetobjects after you get what you want(executing the statement and iterating through the resultset)? What would happen if I "fail" to close either of them? In my webapp I execute a number of statements and I just discovered I never close them or the resultsets. BUT, it works fine testing it(only one user), would problems appear when several users are involved? Should the connectionobject be closed as well after executing just ONE statement, or how to decide when to close the connection? Thanks
Hi, The resultset is automatically closed if u execute the execute() in Statement or if u close the statement and statement is closed when it is garbage collected. But its a good programming practice to close these objects after use. Cheers, vels
Joined: Oct 29, 2001
Thanks, but what about the Connectionobject??? When to dispose of db-connection?
You can close the Db connection whneever you are finished with it. Since your other objects, such as, statement, Resultset, etc. depend on the DB connection, clossing the DB connection will automatically release thos objects too.
Bosun (SCJP, SCWCD)
So much trouble in the world -- Bob Marley