You shouldn't need to inform NH of changes to the domain model. NH is tracking that automatically.
"I am using MVC, but we decide to go explicity as opposed to managing transactions in centralised" Not sure I understand why you would introduce complexity and duplicated code, but that doesn't really have any bearing on the topic. Back too the topic. There are advantages to allowing the client (NH) to managing the database keys. Most of the advantages become apparent when you begin to performance tune NH is high traffic scenarios. technically speaking identity works, but conceptually it does not align to the unit of work concepts -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/FwD3QZqvCDQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
