> > When I browse to table 1, the connection to the database is > closed immediately at the end of the request Yes. > - but the > ResultSet is opened (I assume that the Statement is kept open > too, because closing it would cause a > close() in the corresponding ResultSet) No, closing the connection must close the statements and resultsets.
> When I browse from > table 1 to table 2, the ResultSet of table 1 is closed, right? No, only the connection is closed. > Obviously different RDBMS behave differently because even > when the ResultSet is closed the connection is still opened > in Oracle (in your database it might be closed). Not really. Only the connection is closed. See DataSourceJDBC.close and DataSourceJDBC.closeConnection methods. The JDBC specification says that closing the connection is enough. If you close the connection statements and resultsets are closed automatically. > > As far as I know a ResultSet represents a database cursor. > How can it keep the context to the resource when the > connection is closed? Is this a new JDBC feature which my > driver/DBMS doesn't support? You can't. JDBC specification says that all statements are closed if connection is closed. And all resultsets are closed if statement is closed. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
