Closed superarchi closed 4 years ago
Hi. Sorry for the late reply.
You are right. This is because FileContext stores the data in memory after the initial load. It then writes everything back to disc if anything changes. The cache is shared between multiple instaces of the DbContext. This is reason for the discovered behavior.
Do you have any problems with that behavior?
After disposing of the first context, the second contains the same data.
Example:
I expected exception here