Why is this so hard to set globally!
2 users. conflict. Refresh some interlinked lists? Real tough and ugly code, this is a real world use case!.
And please don't tell me to reload the context! Ideally we need a default MergeOption of AppendNewUpdateExistingUnchangedAndPreserveChanges.
Or atleast a way to set this for the scope of a set of queries (globally). It would also need to cause compiled queries to recompile.
There must be a technical reason that you've made this so hard (and now even harder in 6.1) but in every app I have built in EF for the last 7 years it has been a real nightmare to cope with.
Is this on the radar or am I totally alone in hating this part of EF?
2 users. conflict. Refresh some interlinked lists? Real tough and ugly code, this is a real world use case!.
And please don't tell me to reload the context! Ideally we need a default MergeOption of AppendNewUpdateExistingUnchangedAndPreserveChanges.
Or atleast a way to set this for the scope of a set of queries (globally). It would also need to cause compiled queries to recompile.
There must be a technical reason that you've made this so hard (and now even harder in 6.1) but in every app I have built in EF for the last 7 years it has been a real nightmare to cope with.
Is this on the radar or am I totally alone in hating this part of EF?