I am trying to implement some proper NHibernate session management in my console application, but running into some very weird problems. One moment everything seems to be working fine, but randomly, a
I am creating a large number of entities with NHibernate, attaching them to my ISession, and then using a transaction to commit my changes to the database. Code sample is below:
Can I prevent nhibernate creating new ISessions when lazy loading? How? Correction: I mean new IDbConnections. I have implemented my own DriverConn开发者_StackOverflowectionProvider and I see it gets
My \'user\' entity is almost always retrieved by username, rather than by its integer surrogate key. Beca开发者_StackOverflow社区use the username is not the primary key, this means that the ISession w
NHibernate\'s ISession exposes a method Persist() with two overloads. I cannot find documentation on this method anywhere. It\'s not even mentioned in the NHibernate reference material on http://nhibe
I\'ve just been reading the trace for one of my ASP.NET pages and I\'ve noticed that the page user is being loaded from the database each time the user is required. Since each ISession is supposed to
Is there some way to queue the \"Add\" operation in NHibernate, just like Linq to SQL and Entity Framework does?
I am getting the classic \"object reference not set to an instance of a object\" error on this line HttpContext.Items[\"ISession\"] = Configure.GetSessionFactory().OpenSession();
In this question, the user asks the better way to close sessions because he was having some errors. The most voted answer is Ayende\'s answer that says:
I\'m trying to work out how to complete my implementation of the Repository pattern in an ASP.NET web application.
加载中,请稍侯......