Probably because NHibernate needs to obtain the new version from the DB after each insert, like it does for IDENTITY keys. Something like:
UPDATE MyEntity SET ... WHERE ... SELECT ... FROM MyEntity WHERE ... ... That could be because of different versioning strategies; while some are totally managed on the client, increase a counter or set a timestamp, others are processed on the server, such as SQL Server's ROWVERSION/TIMESTAMP columns, so they need to be retrieved from the database after each update. RP On Wednesday, January 7, 2015 9:07:13 AM UTC, Oleg Meshechkov wrote: > > Hello, > > Could anybody explain me why versioned entities are not batchable? > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
