While merging JPA into Core, Hibernate has reduced the session constructor arguments from 10 to 2, moving the responsibility of providing connection manager, transaction coordinator and the like to an options object.
Porting this in NHibernate looks to me as a prerequisite for porting current Hibernate handling of connections and transactions.
The old obsolete parameter interceptors.beforetransactioncompletion_ignore_exceptions has been dropped by the way and removed from configuration schema.
Frédéric Delaporte June 20, 2017 at 2:09 PM
This is why I have added NH-4034.
Chet June 20, 2017 at 1:37 PM
I agree that it is not a regression, which is good. However, it is confusing since the cloned session's FlushMode is not honored.
Frédéric Delaporte June 20, 2017 at 10:21 AM
Having checked the previous state, this was not supported for child session either. Only the parent session was flushed when committing the NHibernate transaction. Still lacking, but not a regression.
Frédéric Delaporte June 19, 2017 at 6:18 PM
Well it depends... Not from an explicit NHibernate transaction, but will be from a transaction scope. Yes that is a bit lacking.
While merging JPA into Core, Hibernate has reduced the session constructor arguments from 10 to 2, moving the responsibility of providing connection manager, transaction coordinator and the like to an options object.
Porting this in NHibernate looks to me as a prerequisite for porting current Hibernate handling of connections and transactions.