I just integrated NHibernate.Envers into my project. Is there a built in way in Envers where changes are not automatically active, but leaves the old version there until a Publish call is made? Here is the scenario I'm trying to achieve:
Users see Book::Name == "New Book" Admin edits Book::Name to "Old Book" User still sees "New Book" Admin selects Publish All User sees "Old Book" (Hopefully you get the point here, but I'm hoping this is a common scenario) Is there a configuration for Envers to do this natively? If not, is it reasonable that I add a IsPublished flag to the object and use that somehow? The problem with that, is how do I handle the flag, since I cannot go back to the audited version to mark it as false, or another version would be created. Does anyone have experience with this? Thanks! -- 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/-/bk66U42qpXUJ. 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.
