You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article present very little info about tracking. It does answer following questions:
How does tracking affect future queries that query the same entity?
What will happen if I execute for example context.Entities.Where(e => e.Name.StartsWith("zix") twice in the row
How tracking works with TransactionScope and overall with transactions.
Does IsolationLevel of transaction impacts tracking?
What are criteria for LINQ query to return tracking entity and skip SQL query?
Why my query inside RepeatableRead transaction returns cached data from queries outside transaction when I just changed data manually from db side? Why afterwards I have read lock when I am using old tracked entity? It does not make sense - did I make some kind of SQL Query then but it is not updating my entity?
What is lifespan of tracked entities? Do they even have lifespan?
Is there a limit of how many tracked entities EF can have?
Are there any performance considerations we should think about when using tracking?
How can I disable tracking for whole DbContext? Is it possible?
Therefore this article is a stub and it explains nothing of importance.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: f3ffc114-df51-0be7-8972-6fcead14e011
Version Independent ID: 94c34571-7314-aab1-7898-93ac6d0f3430
1. How does tracking affect future queries that query the same entity?
2. What will happen if I execute for example context.Entities.Where(e => e.Name.StartsWith("zix") twice in the row
3. How tracking works with TransactionScope and overall with transactions.
4. Does IsolationLevel of transaction impacts tracking?
5. What are criteria for LINQ query to return tracking entity and skip SQL query?
6. Why my query inside RepeatableRead transaction returns cached data from queries outside transaction when I just changed data manually from db side? Why afterwards I have read lock when I am using old tracked entity? It does not make sense - did I make some kind of SQL Query then but it is not updating my entity?
7. What is lifespan of tracked entities? Do they even have lifespan?
8. Is there a limit of how many tracked entities EF can have?
9. Are there any performance considerations we should think about when using tracking?
10. How can I disable tracking for whole DbContext? Is it possible?
This article present very little info about tracking. It does answer following questions:
context.Entities.Where(e => e.Name.StartsWith("zix")
twice in the rowTransactionScope
and overall with transactions.IsolationLevel
of transaction impacts tracking?RepeatableRead
transaction returns cached data from queries outside transaction when I just changed data manually from db side? Why afterwards I have read lock when I am using old tracked entity? It does not make sense - did I make some kind of SQL Query then but it is not updating my entity?Therefore this article is a stub and it explains nothing of importance.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: