Do I need to call SaveOrUpdate() after calling Merge()?

views:

answers:

+1 Q:

Do I need to call SaveOrUpdate() after calling Merge()?

for reference I'm using version 2.1.2.4000 of Nhibernate.

I've spent pretty much an hour or so reading up the difference between Merge() and SaveOrUpdate() and no explanation attempts to just answer a really simple question??

I know that Merge() will do all the magic to synchronize the detached objects with cached or out of date instances.

BUT, once I've "merged", and I do not intend to change the entity any longer...

Do I have to Still Call SaveOrUpdate?

cheers

Answer here: http://stackoverflow.com/questions/170962/nhibernate-difference-between-session-merge-and-session-saveorupdate

Pierre 303 2010-09-07 07:35:27

that's quite an unhelpful answer. have you read either question fully? and have you read the other answer fully? take particular note of the second comment in the chosen answer.

andy 2010-09-07 07:38:45

Sorry, that was pretty clear to me, but Petr copied the same URL and gave you some details.

Pierre 303 2010-09-07 07:55:20

yep, the clarification and clarity was what I needed

andy 2010-09-07 08:02:16

+2 A:

Check another thread. The point is that Merge() just puts together states from the session (from the database) and your detached object. You then should not use detached object any more but use newly returned object from the session that was merged. This object, of course, has to be "saved or updated" in order to persist changes because it has changed due to Merge operation.

Petr Kozelek 2010-09-07 07:39:43

dude, life saver!

andy 2010-09-07 07:49:18

ansaurus

tags:

views:

answers:

Do I need to call SaveOrUpdate() after calling Merge()?

related questions