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
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,9 @@ The supported types for `T` are:
19
19
20
20
For a detailed explanation of the problem solved by QueryableValues, please continue reading [here][readme-background].
21
21
22
+
> 💡 Still on Entity Framework 6 (non-core)?
23
+
> [This Stack Overflow answer](https://stackoverflow.com/a/70587979/2206145) may be helpful.
24
+
22
25
## When Should You Use It?
23
26
The `AsQueryableValues` extension method is intended for queries that are dependent upon a *non-constant* sequence of external values. In such cases, the underlying SQL query will be efficient on subsequent executions.
Look for the place in your code where you are setting up your [DbContext] and calling the [UseSqlServer] extension method, then use a lambda expression to access the `SqlServerDbContextOptionsBuilder` provided by it. It is on this builder that you must call the `UseQueryableValues` extension method as shown in the following simplified examples:
Copy file name to clipboardExpand all lines: docs/README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,9 @@ The supported types for `T` are:
15
15
16
16
For a detailed explanation of the problem solved by QueryableValues, please continue reading [here][readme-background].
17
17
18
+
> 💡 Still on Entity Framework 6 (non-core)?
19
+
> [This Stack Overflow answer](https://stackoverflow.com/a/70587979/2206145) may be helpful.
20
+
18
21
## When Should You Use It?
19
22
The `AsQueryableValues` extension method is intended for queries that are dependent upon a *non-constant* sequence of external values. In such cases, the underlying SQL query will be efficient on subsequent executions.
Look for the place in your code where you are setting up your [DbContext] and calling the [UseSqlServer] extension method, then use a lambda expression to access the `SqlServerDbContextOptionsBuilder` provided by it. It is on this builder that you must call the `UseQueryableValues` extension method as shown in the following simplified examples:
0 commit comments