There has already been a huge discussion about this here: http://groups.google.com.ar/group/nhusers/browse_thread/thread/11e5ff4c27006c4b/e4326591c21c41fa
It does actually not make much sense to update only a part of your entities in memory. You should not change anything in memory you don't want to be changed. Excerpt from an answer I posted to the forum above (Message 26): "How would to reliably validate entities if you have invalid data in memory? How would you calculate the price of an order when you allow any part of the software changing the price of a product in memory? Your memory needs to be as consistent as the database." On 6 Sep., 14:36, vitalya <[email protected]> wrote: > try to use mutable="false" in the class mapping > > On Sep 5, 6:16 pm, mathmax <[email protected]> wrote: > > > Hello, > > > During a transaction I modify some objects. When I commit the > > transaction, I would like to update only some of them. Is there a > > possibility to define in the mapping file that a class should not be > > updated when the transaction commit? I found the attribute > > update="false" but its only applicable on property tag whereas I would > > like to have something similar for a whole class. > > > Regards, > > > mathmax --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
