Why does identity generator break unit of work in nHibernate? What about EF?
问题 I understand and accept that the identity generator breaks the unit of work because it requires an insert prior when the transaction should actually commit, described in http://fabiomaulo.blogspot.com/2008/12/identity-never-ending-story.html. I'm aware of the alternatives and why they are better (in relation to the problem at hand, and in general). The question I have is why the implementation exists as it does, and whether or not these issues affect EF (sheer curiosity). The only real