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
But I think I found an answer for my original question. Thanks!

On Thu, Jul 7, 2011 at 12:12, Joe Mistachkin <> wrote:

> 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.
> --
> Joe Mistachkin
> _______________________________________________
> sqlite-users mailing list
sqlite-users mailing list

Reply via email to