You just discovered that listeners are executed in order, so you are
on the right track to becoming a Pro.
Secondly, take care the following situations:
1-if you need the id of the entity.
2-if you change values of an entity that didn't change.... You will
force an update.

I am not sure if this is your case but that the reason most of us dont do that.

2011/1/14, ulu <[email protected]>:
> Dearest All,
>
> I published a blog post on automatic updates to the entity just before
> flushing it to the database. Such things are usually used for
> auditing, denormalization, ensuring database consistency etc. I
> believe that my approach is better than what I managed to google, but
> I don't understand that nobody else writes about it. If there are
> NHibernate pros among you, I'll be very grateful for any comments.
>
> The post: http://dotfresh.blogspot.com/2011/01/flush-in-night.html
>
> Thanks
>
> --
> 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.
>
>

-- 
Enviado desde mi dispositivo móvil

-- 
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.

Reply via email to