GenericBatchingBatcher does not apply command changes to the _currentBatch.CurrentStatement

[garashm2k]

We used NHibernateUtil.String.NullSafeSet(cmd, value, index, session); to change command data run-time but when it commits the transaction, the change dose not propagated to _currentBatch.CurrentStatement

we did this change refer to the following article
https://brosteins.com/2014/07/25/sql-server-database-encryption-with-nhibernate-series-part-4-of-5/

[maca88]

This is "by design", CurrentStatement is only used to populate parameters. Currently you have the following options:

• Use NonBatchingBatcherFactory instead
• Use a v5.3 or higher NHibernate (which has IInterceptor.OnPrepareStatement results not used in insert/update commands #2278 fixed), register a custom IInterceptor and try implement the logic inside OnPrepareStatement method. Here you can find an example for it.
• Use a custom sql insert/update

[gtguybrush]

Hi, I too am interested in that approach but first solution is not clear: how can i use NonBatchingBatcherFactory?

in the code there are only reference to NHibernateUtil.String.NullSafeSet(cmd, value, index);

[fredericDelaporte]

By default, the batcher is chosen by the the NHibernate driver you are using (which can be chosen by the dialect), provided you have a batchSize greater than 1 (otherwise it will be the NonBatchingBatcherFactory anyway). These things are configurable, see adonet.factory_class and adonet.batch_size.

[maca88]

how can i use NonBatchingBatcherFactory?

by setting the xml configuration property adonet.factory_class to NHibernate.AdoNet.NonBatchingBatcherFactory, NHibernate or by code:

var cfg = new NHibernate.Cfg.Configuration();
cfg.SetProperty(Environment.BatchStrategy, typeof(NonBatchingBatcherFactory).AssemblyQualifiedName);