----- Original Message ----- From: "Henner Kollmann" <[EMAIL PROTECTED]> To: "'Jan-Friedrich Mutter'" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, March 31, 2004 8:25 PM Subject: AW: [dbforms] still connections not closed
> > > > The maxium of opened ResultSets is the number of tables which > > I have in my DB Schema, not dependend on the number of users. > > Is that right? > No, the maximum number of opened ResultSets depends on the number of pages > you open simultanious without running into session time out. Ok, I see. When I browse to table 1, the connection to the database is closed immediately at the end of the request - 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) When I browse from table 1 to table 2, the ResultSet of table 1 is closed, right? 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). 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? - Jan. ------------------------------------------------------- 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
