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
Each time a user injects the instance and reuses it, it creates a build that continues to the second query.
For instance: qb.Where(d => d.id == 1).ExecuteSingleAsync(); qb.ExecuteSingleAsync();
Both of these will return the same value because the where is carried on to the second query as well.
Possible solution:
qb should be a factory that only offers one Instance option which then can be manipulated.
Like so:
The problem:
Each time a user injects the instance and reuses it, it creates a build that continues to the second query.
For instance:
qb.Where(d => d.id == 1).ExecuteSingleAsync();
qb.ExecuteSingleAsync();
Both of these will return the same value because the where is carried on to the second query as well.
Possible solution:
qb should be a factory that only offers one Instance option which then can be manipulated.
Like so:
qb.Builder.Where(d => d.id == 1).ExecuteSingleAsync();
qb.Builder.ExecuteSingleAsync();
The text was updated successfully, but these errors were encountered: