Thanks for the hint. Using a separate data context for the other thread
solves the problem. But it doesn't make the situation much better, because
the data context seem to have separate cashes. So it does not help to cash
stuff in the background, because it won't be ready for the main thread
I do not see anything obviously wrong with using the same connection
to construct two or more LINQ data contexts; however, my knowledge of
LINQ and its use of threads is somewhat limited.
sqlite-users mailing list
I probably am using a single SQLiteDataReader, although I
never explicitly handle one.
context = new DataContext(_connection);
I do all queries on such a table object via Linq. Is there a way to
control the DataReader involved with such a query?
On Thu, Jul 7, 2011 at
Benjamin Savs wrote:
If I run Linq-queries from several threads I will get an exception that
"*DataReader has been closed*". Is this normal or should there be a way to
Are you trying to share a single SQLiteDataReader object instance between
or just the
Mail list logo