Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Throw DbUpdateException or DbUpdateConcurrencyException for in-memory database errors #23569

Closed
ajcvickers opened this issue Dec 3, 2020 · 1 comment
Closed

Throw DbUpdateException or DbUpdateConcurrencyException for in-memory database errors #23569

ajcvickers opened this issue Dec 3, 2020 · 1 comment
Labels
closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed.

Comments

@ajcvickers
Copy link
Contributor

See

Adding_the_same_entity_twice_results_in_DbUpdateException
Deleting_the_same_entity_twice_results_in_DbUpdateConcurrencyException
Deleting_then_updating_the_same_entity_results_in_DbUpdateConcurrencyException
@ajcvickers ajcvickers added area-in-memory area-save-changes type-enhancement good first issue This issue should be relatively straightforward to fix. labels Dec 3, 2020
@ajcvickers ajcvickers added this to the Backlog milestone Dec 4, 2020
FelicePollano added a commit to FelicePollano/efcore that referenced this issue Dec 27, 2020
@FelicePollano
added unit test for dotnet#23569
fcfab10
FelicePollano added a commit to FelicePollano/efcore that referenced this issue Dec 27, 2020
@FelicePollano
fixed issue dotnet#23569
29bb53f
@FelicePollano FelicePollano mentioned this issue Dec 27, 2020
Closed
@AndriySvyryd AndriySvyryd mentioned this issue Jan 14, 2022
Closed
12 tasks
@ajcvickers ajcvickers added propose-close closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. and removed type-enhancement propose-close good first issue This issue should be relatively straightforward to fix. area-in-memory area-save-changes labels Oct 20, 2022
@ajcvickers
Copy link
Contributor Author

We recommend against using the in-memory provider for testing--see Testing EF Core Applications. While we have no plans to remove the in-memory provider, we will not be adding any new features to this provider because we believe valuable development time is better spent in other areas. When feasible, we plan to still fix regressions in existing behavior.

@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2022
@ajcvickers ajcvickers removed this from the Backlog milestone Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed.
Projects
None yet
Milestone
No milestone
1 participant
@ajcvickers