Frédéric Delaporte

The firebird driver still has a method, `ClearPool`, which uses reflection while it does no more need to, since it now has a direct reference on the data provider.

I have tested with a dummy mvc project, referencing the resulting Nuget packages (from a local repository) for NHibernate and SqlServer. It works.

We do not actually publish them, so it should not cause issues. Of course for testing with local repositories, this could cause issues. But since only contributors will likely do...

> We can still do this, but without breaking changes, just by providing relevant NHibernate.Driver.WhateverDB packages in addition to built-in providers. Meaning we would keep all the reflection based drivers...

Maybe NHibernate drivers needs to target the lowest data provider version possible, and let user choose to use a newer one if he wishes. But for supporting NetStandard 2.0, the...

Be it for Npgsql or Oracle, if we need to upgrade for some reason, I do not think the failures they introduce should prevent us of upgrading. We should instead...

Hi, > > The doc/reference needs some updates, especially the driver setting documentation. > > I would be inclined to do the documentation as a second pull request once I...

There is a conflict with #2964 to resolve.

Maybe because it seems unlikely to contributors this has anything to do with NHibernate. If things actually land into DB although the scope is not committed, while used connections were...

> It used to be that an NHibernate session should always have an NHibernate transaction, even if there is an outer TransactionScope. It appears you don't. I haven't kept up...