[NHibernate-development] [hibernate-dev] Connection release modes

[Steve Ebersole]

How did that lead to a discussion of connection release modes ;)

Mmm, I'd have to look through the code; *but* a load & lock operation
makes no sense in an auto-commit scenario; so I'd assume it has to do
with that...

-----Original Message-----
From: hibernate-dev-bounces at lists.jboss.org
[mailto:hibernate-dev-bounces at lists.jboss.org] On Behalf Of Sergey
Koshcheyev
Sent: Wednesday, December 13, 2006 11:11 AM
To: the NHibernate development list
Cc: hibernate
Subject: Re: [NHibernate-development] [hibernate-dev] Connection release
modes

Steve Ebersole wrote:
> I don't understand the statement about "auto-commit mode connection
> release".  The idea with the implied auto-commit connection release
mode
> is that in the case of auto-commit transaction control, there is
really
> no need to have the same connection for each operation as long as we
are
> not batching and not generally holding open JDBC resources.  What
makes
> you say it appears to happen for just a few operations?

I guess I worded that badly. To put it in source code terms: in
SessionImpl.get(String entityName, Serializable id) there is a call to
SessionImpl.afterOperation. There is no such call in
SessionImpl.get(String entityName, Serializable id, LockMode lockMode).
Is this a mistake or is the call not needed in the second case for some
reason?

Sergey
_______________________________________________
hibernate-dev mailing list
hibernate-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev