>>We're having a debate about whether to use EF AddOrUpdate.
>>
>>According to Julie Lerman at http://thedatafarm.com/data-access/take-care-with-ef-4-3-addorupdate-method/ you should only use AddOrUpdate when doing Data Migrations during development.
>>
>>My co-workers are saying that using AddOrUpdate is acceptable even though it makes a round trip query to the database to see if the record exists in order to determine whether it creates an update or an insert command. I've seen that in SQL Profiler.
>>
>>And Julie makes other arguments against its use as well.
>>
>>Thanks.
>
>The generated SQL code at the bottom of the blog post is quite strange.
>
>BTW, for SQL 2008 and up the update or insert should be done with MERGE and in this case this method will be OK.

To be fair, most of the SQL generated from EF is strange.