Effort throws InvalidOperationException: Sequence contains more than one matching element

c# effort entity-framework

Popular Answer

I discovered that using a different connection helped me with this problem.Effort.DbConnectionFactory.CreatePersistent ) for each situation resolved the problem.

Since each context in my scenario runs across entirely independent tables, there shouldn't have been a conflict in Effort/NMemory; hence, I believe the bug report to be valid. Nevertheless, this knowledge might help some others in the interim.

The trade-off is that this might be signaling to you that you actually are running two contexts on the same table, which would be problematic. As a result, you'll need to be on the lookout for this as well.

1
2/6/2017 7:47:14 PM


Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow