-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: LINQ3
-
None
-
None
-
Dotnet Drivers
-
None
-
None
-
None
-
None
-
None
-
None
There seems to be a potential performance issue when moving from LINQ2 to the LINQ3 provider. As seen in the community post here, this needs to be checked whether this is due to some known issues or a regression in the newer provider due to a change.