There were some discussions on the old forum about this but I can't find them now. I remember that it was frowned upon to create multiple ISession instances that used the same database connection but I don't remember exactly why. If you manage your own connections, as I do, then could I create a single connection and use that in more than one ISession? This app will not use multiple threads so there wouldn't be more than one chunk of code attempting to do anything with the connection at the same time.

Thx...

benster

You may reuse connections, just note that NHibernate disables second-level cache when using a user-supplied connection. This can be avoided if you write your own IConnectionProvider.

Thanx Sergey - my question really is around having multiple ISession instances using a single connection at once. I understand that I can reuse them but I wondered if I can have a single connection that's used by more than one long-running ISession at once.

Specifically, what technical reasons are there in NH that would preclude this? We won't be spawning threads for these sessions but the app is a WinForms app that would benefit from having multiple long-running sessions for different modules in the app. If these could use the same connection (since they will not be spawning transactions at the same time) then that would be a good thing.

Any thoughts?

benster