Concurrent read access in Entity Framework 4

Question

Assuming I am never writing with EF, will never call SaveChanges for example, Is EF safe for concurrent reads from the same ObjectContext?

It may still be initialising a database connection and reading new objects, or updating existing objects (or deleting!) but it won't be writing anything to the db, so no transactions (I assume).

Thanks

Ladislav Mrnka · Accepted Answer · 2012-04-13 14:10:58Z

2

ObjectContext and related EF classes are not thread safe so don't use them for concurrent operations. If you need to run concurrent data access use a new context for every thread.

answered Apr 13, 2012 at 14:10

Ladislav Mrnka

365k60 gold badges666 silver badges673 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Ian Over a year ago

Perfect, I sort of assumed they weren't, but I am forever the optimist :)

Collectives™ on Stack Overflow

Concurrent read access in Entity Framework 4

1 Answer 1

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Related