We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When working with Entity Framework or EntityFramework Core, there needs to be a way to skip the implicit call to SaveChanges or SaveChangesAsync
SaveChanges
SaveChangesAsync
Proposed options:
Option 1 - New IImmediateRepository and IReadOnlyImmediateRepository interfaces to support the immediate save changes
IImmediateRepository
IReadOnlyImmediateRepository
Example:
// currently await _thingsRepo.AddAsync(newThing); // instead await _thingsRepo.AddImmediateAsync(newThing);
Where the existing methods will not immediately call for SaveChanges until UpdateAsync is called
UpdateAsync
Option 2 - optional parameter to apply immediately
// currently applying immediately await _thingsRepo.AddAsync(newThing); await _thingsRepo.AddAsync(newThing, applyImmediately: true);
The text was updated successfully, but these errors were encountered:
Option 2 seems to be looking better to me right about now
Sorry, something went wrong.
No branches or pull requests
When working with Entity Framework or EntityFramework Core, there needs to be a way to skip the implicit call to
SaveChanges
orSaveChangesAsync
Proposed options:
Option 1 - New
IImmediateRepository
andIReadOnlyImmediateRepository
interfaces to support the immediate save changesExample:
Where the existing methods will not immediately call for SaveChanges until
UpdateAsync
is calledOption 2 - optional parameter to apply immediately
The text was updated successfully, but these errors were encountered: