Thanks Oskar for prompt response. I want to make sure that I got you right.
So, what is meant by "database connection" here is provided database connections not those opened & controlled by NHibernate. right? In other words, If i opened a session with a provided database connection I should not share it among other concurrent sessions or transactions. On Sep 9, 6:45 pm, Oskar Berggren <[email protected]> wrote: > In same process. And since two different processen cannot have the > same connection, the conclusion is "never". The session "owns" the > connection. Nothing in NHibernate prevents you from having multiple > concurrent sessions each using a different connection to the same > database, however. > > /Oskar > > 2009/9/9 waheedsayed <[email protected]>: > > > > > > > In NHibernate 1.2GA Documenations and also in NHibernate 2.1.0GA > > Documentation, I couldn't understand the following statement. > > > ------- > > Chapter 10. Transactions And Concurrency > > > 10.2. Threads and connections > > >>> Never create more than one concurrent ISession or ITransaction instance > >>> per database connection. > > ------- > > > What is the context of this restriction? In same method? In same > > thread? In same application? or what?! > > Why not? What may happen If I did so? > > > Thanks & Regards --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
