Ok thx for the replies, one more question. :) I still do not understand something: - when I explicitely call 'Disconnect' to close the DB connection (which I understand is obsolete), NHibernate is not able (or just doesn't) reconnect implicitely when necessary. - when I do not call Disconnect, but use the 'after_transaction' connection-release mode, NH disconnects the session from the DB after the transaction has completed. When NH needs to access the DB again, it reconnects implicitely. (For instance, in a lazy-loading case: I retrieve an object within a transaction. When the transaction is committed, the connection is closed. A few seconds later, I need the lazy collection: NHibernate connects the session, retrieves the collection and disconnects the session again (I'm not sure about this last one :) ).
Why is this behaviour different ? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
