I know there is a option to always select before update. maybe one exists for always select after save. if so i would set this in the mapping. this way you don't need to think about it in your domain. this would happen every time you commit a modification to the entity so you need to consider that.
you may also be able to use a postinsert and postupdate event listener (maybe after commit transaction would be better). verify the typeof entity and evict/get from session. this keeps the functionality in the infrastructure so the domain remains clean. On Nov 13, 10:31 am, Jason Grundy <[email protected]> wrote: > Thanks for the reply Jason M. I appreciate that there are alternatives > to a trigger within NHibernate but, for the sake of this discussion, > can we just assume that the trigger is something that can not be > changed? > > The "Post-Redirect-Get" approach that you outline does not violate CQS > and that is actually what I am doing. I was simply wondering whether > within a single UoW there is an alternative to the Flush-Evit-Get > triumvirate? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. 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 -~----------~----~----~----~------~----~------~--~---
