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
{{ message }}
This repository was archived by the owner on Feb 1, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,10 +80,7 @@ using (var dc = options.CreateLinqToDbConnection())
80
80
}
81
81
```
82
82
83
-
You can use all `LINQ To DB` extension functions in your EF linq queries. Just ensure you have called `ToLinqToDB()` function before materializing objects for synchronous methods.
84
-
85
-
Since EF Core have defined it's own asynchronous methods, we have to duplicate them to avoid naming collisions.
86
-
Async methods have the same name but with `LinqToDB` suffix. E.g. `ToListAsyncLinqToDB()`, `SumAsyncLinqToDB()`, ect.
83
+
You can use all `LINQ To DB` extension functions in your EF linq queries. Just ensure you have called `ToLinqToDB()` function before materializing objects.
87
84
88
85
```cs
89
86
using (varctx=CreateAdventureWorksContext())
@@ -112,8 +109,8 @@ using (var ctx = CreateAdventureWorksContext())
112
109
// ensure we have replaced EF context
113
110
varitems1=neededRecords.ToLinqToDB().ToArray();
114
111
115
-
//we have to call our method to avoid naming collisions
0 commit comments