Hello forum,

A newbie question. Open a session implies that a connection is openned?

Yes. Or at least retrieved from a pool.

A connection is NOT opened when a session is opened. The connection will be opened when it is needed. When the connection is closed depends on your connection release mode. So a connection may be opened and closed with each data operation on the session.

I guess you're right. The thing is I use automatic tx demarcation which immediately issues a transaction "begin" which I think needs a db connection (or maybe it's "lazily" managed, but I don't think so).

Unless you pass a connection to it like we do in our application...

benster

So, what about lazy initialitation. If no session is opened, my program will crash because there isn't any session opened. When I get a customer(for example), I open a session and when I have obtained the customer I close the session. So when I access to customer Contacts (lazy="true", it's required) from my program, the session is closed and Contacts won't be loaded correctly, my program will crash!!!

How do you design your software?
How do you take care about this situation?

Thanks in advance.

jeusdi,

This is a common concern in Hibernate. The documentation, http://www.hibernate.org/hib_docs/nhibernate/html/collections.html#collections-lazy , lists the basic ways of dealing with this.

Basically, you can either force NHibernate to load all the data before closing the session, or open a new session to load the data. If you open a new session, you need to attach the customer object to the new session using ISession.Lock() or ISession.Update(). Which of these methods you use will depend on your application and data.

The rewarded answer was "Yes. Or at least retrieved from a pool." looks to be technically wrong. I don't know if the point he received for answering should be deducted or not ;-)