You can open/close the connection using session.Disconnect()/Reconnect() which is recommended if you hang on to the session for a while.
If you use long lived session I agree that it might feel better if the created session was closed (disconnected).to start with. I guess the choosen path is chosen due to the "normal handling" of session which is short lived. ________________________________________ Från: [email protected] [EMAIL PROTECTED] för Joe [EMAIL PROTECTED] Skickat: den 1 oktober 2008 23:04 Till: nhusers Ämne: [nhusers] Understanding how NH handles database connections I am trying to understand how NH handles the actual ADO.NET connection. For example, when I request ISession.Connection, I get an OPEN IDbConnection. The connection appears to stay open until ISession.Close is called. Is this the expected behavior? I was trying to use the ADO connection provided by NH and was surprised to find it already opened. I was expecting to have to open and close the connection. If I need to use the connection from ISession, should I not worry about opening and closing it? Thanks, Joe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
